[Skip to Content]

HTML Document

URL: https://vector-rev.blogspot.is/2017/07/blog-post_16.html
HTTP Status: 200 OK
MIME Type: text/html
Last Modified: Wed, 12 Jul 2017 09:48:08 GMT
Download Time: Less than a second
Cookies: None
Size: 72 KB
Page Weight: 115 KB (total size of HTML, CSS, JavaScript and images)
Depth: 1 clicks from home page
Charset: utf-8
Forms: 3 forms containing 10 controls
HTTP Headers: View Headers 7 headers
Links In: View Links 1 pages
Links Out: View Links 50 links
Images: View Images 19 images
CSS: View CSS Files 0 files
JavaScript: View JavaScript Files 0 files
  
Issue Issues: 61 issues found on 266 lines
Priority 1
Google recommends separating keywords in URLs by dashes instead of underscores.
Dashes perform better than underscores in Google as keyword separators, and underscores perform better than no separators.
Line 1 Google
Priority 3
No meta description tag found. Use a description tag that accurately describes the contents of a web page.
A well-written meta description attracts more clicks in search results than an irrelevant or missing description.
Priority 1
Have a link labeled 'Home' on every page on the site, except for the home page.
Many sites place the organization's logo on the top of every page and link it to the homepage. While many users expect logos are clickable, around 25% will not realize that links to the homepage. Therefore, include a link labeled 'Home' near the top of the page to help those users.

1<!DOCTYPE html>

Priority 1
Use the LANG attribute to identify the language of the page.
In HTML add a LANG attribute to the HTML tag, and in PDF set the language using Document Properties in Acrobat. This allows screen readers to pronounce words correctly.
Priority 1
Attribute 'xmlns:b' not allowed on element.
Line 2 HTML5

2<html class='v2' dir='ltr' xmlns='http://www.w3.org/1999/xhtml' xmlns:b='http://www.google.com/2005/gml/b' xmlns:data='http://www.google.com/2005/gml/data' xmlns:expr='http://www.google.com/2005/gml/expr'>

3<head>

4<link type='text/css' rel='stylesheet' href='https://www.blogger.com/static/v1/widgets/2258130529-css_bundle_v2.css' />

5<meta content='width=1100' name='viewport'/>

6<meta content='text/html; charset=UTF-8' http-equiv='Content-Type'/>

7<meta content='blogger' name='generator'/>

8<link href='https://vector-rev.blogspot.is/favicon.ico' rel='icon' type='image/x-icon'/>

9<link href='https://vector-rev.blogspot.com/2017/07/blog-post_16.html' rel='canonical'/>

10<link rel="alternate" type="application/atom+xml" title="Векторная теория социальной революции - Atom" href="https://vector-rev.blogspot.com/feeds/posts/default" />

11<link rel="alternate" type="application/rss+xml" title="Векторная теория социальной революции - RSS" href="https://vector-rev.blogspot.com/feeds/posts/default?alt=rss" />

Priority 1
Bad value for attribute 'rel'. Bad value 'service.post'. The string 'service.post' is not a registered keyword or absolute URL.
Line 12 HTML5

12<link rel="service.post" type="application/atom+xml" title="Векторная теория социальной революции - Atom" href="https://www.blogger.com/feeds/8956464986740803789/posts/default" />

13

14<link rel="alternate" type="application/atom+xml" title="Векторная теория социальной революции - Atom" href="https://vector-rev.blogspot.com/feeds/4865024095207574136/comments/default" />

15<!--[if IE]><script type="text/javascript" src="https://www.blogger.com/static/v1/jsbin/3409755933-ieretrofit.js"></script>

16<![endif]-->

17<link href='https://img.youtube.com/vi/kAUS8pav1sw/hqdefault.jpg' rel='image_src'/>

18<meta content='https://vector-rev.blogspot.com/2017/07/blog-post_16.html' property='og:url'/>

19<meta content='Читатели книги &quot;Векторная теория социальной революции&quot;' property='og:title'/>

20<meta content='Векторная теория социальной революции' property='og:description'/>

21<meta content='https://lh6.googleusercontent.com/proxy/-5LzHID3JZ8E6ktfRig5OT6zC01W3beLn5mdQiRnfHryxxooxKOPa9GP-TZYhwO2TTTMSlx9Kr7Rbvx9ryTdCNQmcsNpYsld=w1200-h630-n-k-no-nu' property='og:image'/>

22<!--[if IE]> <script> (function() { var html5 = ("abbr,article,aside,audio,canvas,datalist,details," + "figure,footer,header,hgroup,mark,menu,meter,nav,output," + "progress,section,time,video").split(','); for (var i = 0; i < html5.length; i++) { document.createElement(html5[i]); } try { document.execCommand('BackgroundImageCache', false, true); } catch(e) {} })(); </script> <![endif]-->

Priority 2
Title element is too long for Bing. Bing recommends using titles up to 65 characters long. The title is 93 characters long.
The major search engines all have different limits for title length, and these limits have changed over time. Avoid title lengths close to the limits to prevent problems when the limits change again, and note that the W3C recommends a maximum length of 64 characters.
Line 23 Bing
Priority 2
Title element is too long for Yahoo. Yahoo recommends limiting your page title to 67 characters. The title is 93 characters long.
The major search engines all have different limits for title length, and these limits have changed over time. Avoid title lengths close to the limits to prevent problems when the limits change again, and note that the W3C recommends a maximum length of 64 characters.
Line 23 Yahoo

23<title>Векторная теория социальной революции: Читатели книги "Векторная теория социальной революции"</title>

24<style id='page-skin-1' type='text/css'><!--

25/*-----------------------------------------------

26Blogger Template Style

27Name: Picture Window

28Designer: Blogger

29URL: www.blogger.com

30----------------------------------------------- */

31/* Variable definitions

32====================

33<Variable name="keycolor" description="Main Color" type="color" default="#1a222a"/>

34<Variable name="body.background" description="Body Background" type="background"

35color="#d8d8d8" default="#111111 url(//themes.googleusercontent.com/image?id=1OACCYOE0-eoTRTfsBuX1NMN9nz599ufI1Jh0CggPFA_sK80AGkIr8pLtYRpNUKPmwtEa) repeat-x fixed top center"/>

36<Group description="Page Text" selector="body">

37<Variable name="body.font" description="Font" type="font"

38default="normal normal 15px Arial, Tahoma, Helvetica, FreeSans, sans-serif"/>

39<Variable name="body.text.color" description="Text Color" type="color" default="#333333"/>

40</Group>

41<Group description="Backgrounds" selector=".body-fauxcolumns-outer">

42<Variable name="body.background.color" description="Outer Background" type="color" default="#296695"/>

43<Variable name="header.background.color" description="Header Background" type="color" default="transparent"/>

44<Variable name="post.background.color" description="Post Background" type="color" default="#ffffff"/>

45</Group>

46<Group description="Links" selector=".main-outer">

47<Variable name="link.color" description="Link Color" type="color" default="#336699"/>

48<Variable name="link.visited.color" description="Visited Color" type="color" default="#6699cc"/>

49<Variable name="link.hover.color" description="Hover Color" type="color" default="#33aaff"/>

50</Group>

51<Group description="Blog Title" selector=".header h1">

52<Variable name="header.font" description="Title Font" type="font"

53default="normal normal 36px Arial, Tahoma, Helvetica, FreeSans, sans-serif"/>

54<Variable name="header.text.color" description="Text Color" type="color" default="#ffffff" />

55</Group>

56<Group description="Tabs Text" selector=".tabs-inner .widget li a">

57<Variable name="tabs.font" description="Font" type="font"

58default="normal normal 15px Arial, Tahoma, Helvetica, FreeSans, sans-serif"/>

59<Variable name="tabs.text.color" description="Text Color" type="color" default="#ffffff"/>

60<Variable name="tabs.selected.text.color" description="Selected Color" type="color" default="#094c8c"/>

61</Group>

62<Group description="Tabs Background" selector=".tabs-outer .PageList">

63<Variable name="tabs.background.color" description="Background Color" type="color" default="transparent"/>

64<Variable name="tabs.selected.background.color" description="Selected Color" type="color" default="transparent"/>

65<Variable name="tabs.separator.color" description="Separator Color" type="color" default="transparent"/>

66</Group>

67<Group description="Post Title" selector="h3.post-title, .comments h4">

68<Variable name="post.title.font" description="Title Font" type="font"

69default="normal normal 18px Arial, Tahoma, Helvetica, FreeSans, sans-serif"/>

70</Group>

71<Group description="Date Header" selector=".date-header">

72<Variable name="date.header.color" description="Text Color" type="color" default="#000000"/>

73</Group>

74<Group description="Post" selector=".post">

75<Variable name="post.footer.text.color" description="Footer Text Color" type="color" default="#999999"/>

76<Variable name="post.border.color" description="Border Color" type="color" default="#dddddd"/>

77</Group>

78<Group description="Gadgets" selector="h2">

79<Variable name="widget.title.font" description="Title Font" type="font"

80default="bold normal 13px Arial, Tahoma, Helvetica, FreeSans, sans-serif"/>

81<Variable name="widget.title.text.color" description="Title Color" type="color" default="#888888"/>

82</Group>

83<Group description="Footer" selector=".footer-outer">

84<Variable name="footer.text.color" description="Text Color" type="color" default="#cccccc"/>

85<Variable name="footer.widget.title.text.color" description="Gadget Title Color" type="color" default="#aaaaaa"/>

86</Group>

87<Group description="Footer Links" selector=".footer-outer">

88<Variable name="footer.link.color" description="Link Color" type="color" default="#99ccee"/>

89<Variable name="footer.link.visited.color" description="Visited Color" type="color" default="#77aaee"/>

90<Variable name="footer.link.hover.color" description="Hover Color" type="color" default="#33aaff"/>

91</Group>

92<Variable name="content.margin" description="Content Margin Top" type="length" default="20px" min="0" max="100px"/>

93<Variable name="content.padding" description="Content Padding" type="length" default="0" min="0" max="100px"/>

94<Variable name="content.background" description="Content Background" type="background"

95default="transparent none repeat scroll top left"/>

96<Variable name="content.border.radius" description="Content Border Radius" type="length" default="0" min="0" max="100px"/>

97<Variable name="content.shadow.spread" description="Content Shadow Spread" type="length" default="0" min="0" max="100px"/>

98<Variable name="header.padding" description="Header Padding" type="length" default="0" min="0" max="100px"/>

99<Variable name="header.background.gradient" description="Header Gradient" type="url"

100default="none"/>

101<Variable name="header.border.radius" description="Header Border Radius" type="length" default="0" min="0" max="100px"/>

102<Variable name="main.border.radius.top" description="Main Border Radius" type="length" default="20px" min="0" max="100px"/>

103<Variable name="footer.border.radius.top" description="Footer Border Radius Top" type="length" default="0" min="0" max="100px"/>

104<Variable name="footer.border.radius.bottom" description="Footer Border Radius Bottom" type="length" default="20px" min="0" max="100px"/>

105<Variable name="region.shadow.spread" description="Main and Footer Shadow Spread" type="length" default="3px" min="0" max="100px"/>

106<Variable name="region.shadow.offset" description="Main and Footer Shadow Offset" type="length" default="1px" min="-50px" max="50px"/>

107<Variable name="tabs.background.gradient" description="Tab Background Gradient" type="url" default="none"/>

108<Variable name="tab.selected.background.gradient" description="Selected Tab Background" type="url"

109default="url(https://resources.blogblog.com/blogblog/data/1kt/transparent/white80.png)"/>

110<Variable name="tab.background" description="Tab Background" type="background"

111default="transparent url(https://resources.blogblog.com/blogblog/data/1kt/transparent/black50.png) repeat scroll top left"/>

112<Variable name="tab.border.radius" description="Tab Border Radius" type="length" default="10px" min="0" max="100px"/>

113<Variable name="tab.first.border.radius" description="First Tab Border Radius" type="length" default="10px" min="0" max="100px"/>

114<Variable name="tabs.border.radius" description="Tabs Border Radius" type="length" default="0" min="0" max="100px"/>

115<Variable name="tabs.spacing" description="Tab Spacing" type="length" default=".25em" min="0" max="10em"/>

116<Variable name="tabs.margin.bottom" description="Tab Margin Bottom" type="length" default="0" min="0" max="100px"/>

117<Variable name="tabs.margin.sides" description="Tab Margin Sides" type="length" default="20px" min="0" max="100px"/>

118<Variable name="main.background" description="Main Background" type="background"

119default="transparent url(https://resources.blogblog.com/blogblog/data/1kt/transparent/white80.png) repeat scroll top left"/>

120<Variable name="main.padding.sides" description="Main Padding Sides" type="length" default="20px" min="0" max="100px"/>

121<Variable name="footer.background" description="Footer Background" type="background"

122default="transparent url(https://resources.blogblog.com/blogblog/data/1kt/transparent/black50.png) repeat scroll top left"/>

123<Variable name="post.margin.sides" description="Post Margin Sides" type="length" default="-20px" min="-50px" max="50px"/>

124<Variable name="post.border.radius" description="Post Border Radius" type="length" default="5px" min="0" max="100px"/>

125<Variable name="widget.title.text.transform" description="Widget Title Text Transform" type="string" default="uppercase"/>

126<Variable name="mobile.background.overlay" description="Mobile Background Overlay" type="string"

127default="transparent none repeat scroll top left"/>

128<Variable name="startSide" description="Side where text starts in blog language" type="automatic" default="left"/>

129<Variable name="endSide" description="Side where text ends in blog language" type="automatic" default="right"/>

130*/

131/* Content

132----------------------------------------------- */

Priority 2
Ensure that foreground and background colors have enough contrast. The foreground to background color contrast ratio is 1. CSS color: 0, 0, 0; background-color: 0, 0, 0; font-size: pt; font-weight:

Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background.

  • The contrast ratio should be 3.0 or more for 18 point text, or larger
  • The contrast ratio should be 3.0 or more for 14 point bold text, or larger
  • The contrast ratio should be 4.5 or more for all other text
Priority 3
Search engines may penalize invisible text where text color is nearly identical to the background color. The foreground/background luminosity ratio is
Line 133 Google Yahoo Bing

133body {

Priority 2
Use relative rather than absolute units in CSS property values.
Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users, and a lot of people over 50, increase the browser default font size to make text easier to read. Absolute units ignore this user choice. Relative units like EM and percentages "stretch" according to the screen size and/or user's preferred font size, and work on a large range of devices.

134font: normal normal 15px Arial, Tahoma, Helvetica, FreeSans, sans-serif;

135color: #000000;

136background: #000000

Priority 2
Use background images sparingly and make sure they are simple, especially behind text.
Background images can make it difficult for users to read foreground text. A single, large, complex background image (including a picture) can substantially slow page download rates.

url(//themes.googleusercontent.com/image?id=1fPzKKjY9pDchHIeFXfLO2zY1SYfTku0PLrkb-Aiu7meqodh01WKnpNCHAuTcBrMZaM6D) repeat-x scroll top center /* Credit: imagedepotpro (http://www.istockphoto.com/file_closeup.php?id=4489297&platform=blogger) */;

137}

138html body .region-inner {

139min-width: 0;

140max-width: 100%;

141width: auto;

142}

143.content-outer {

144font-size: 90%;

145}

Priority 1
Removing the underline from links makes it hard for color-blind users to see them.
Remove the text-decoration:none property from your link styles, or add other non-color style attributes to visually distinguish links.

146a:link {

147text-decoration:none;

148color: #094c8c;

149}

150a:visited {

151text-decoration:none;

152color: #922283;

153}

154a:hover {

155text-decoration:underline;

156color: #cc0000;

157}

158.content-outer {

159background: transparent url(https://resources.blogblog.com/blogblog/data/1kt/transparent/white80.png) repeat scroll top left;

Priority 6
Property -moz-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 160 CSS Validation

160-moz-border-radius: 15px;

Priority 6
Property -webkit-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 161 CSS Validation

161-webkit-border-radius: 15px;

Priority 6
Property -goog-ms-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 162 CSS Validation

162-goog-ms-border-radius: 15px;

Priority 3
CSS property border-radius is not supported by IE8 or earlier.
No rounded corners will be displayed on old versions of Internet Explorer.

163border-radius: 15px;

Priority 6
Property -moz-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 164 CSS Validation

164-moz-box-shadow: 0 0 3px rgba(0, 0, 0, .15);

Priority 6
Property -webkit-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 165 CSS Validation

165-webkit-box-shadow: 0 0 3px rgba(0, 0, 0, .15);

Priority 6
Property -goog-ms-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 166 CSS Validation

166-goog-ms-box-shadow: 0 0 3px rgba(0, 0, 0, .15);

Priority 3
The box-shadow CSS property is not supported in Internet Explorer 8 and Safari 5.0 or earlier.
Boxes will display without a shadow in old versions of Internet Explorer and Safari.

167box-shadow: 0 0 3px rgba(0, 0, 0, .15);

168margin: 30px auto;

169}

170.content-inner {

171padding: 15px;

172}

173/* Header

174----------------------------------------------- */

175.header-outer {

176background: #040528 url(https://resources.blogblog.com/blogblog/data/1kt/transparent/header_gradient_shade.png) repeat-x scroll top left;

Priority 2
The CSS underscore filter hack no longer works in IE7 or later.
Underscored property names are treated as custom properties in IE7. Conditional comments are a fully supported, standards-compliant alternative.
Priority 6
Property _background-image is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 177 CSS Validation

177_background-image: none;

178color: #ffffff;

Priority 6
Property -moz-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 179 CSS Validation

179-moz-border-radius: 10px;

Priority 6
Property -webkit-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 180 CSS Validation

180-webkit-border-radius: 10px;

Priority 6
Property -goog-ms-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 181 CSS Validation

181-goog-ms-border-radius: 10px;

Priority 3
CSS property border-radius is not supported by IE8 or earlier.
No rounded corners will be displayed on old versions of Internet Explorer.

182border-radius: 10px;

183}

184.Header img, .Header #header-inner {

Priority 6
Property -moz-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 185 CSS Validation

185-moz-border-radius: 10px;

Priority 6
Property -webkit-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 186 CSS Validation

186-webkit-border-radius: 10px;

Priority 6
Property -goog-ms-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 187 CSS Validation

187-goog-ms-border-radius: 10px;

Priority 3
CSS property border-radius is not supported by IE8 or earlier.
No rounded corners will be displayed on old versions of Internet Explorer.

188border-radius: 10px;

189}

190.header-inner .Header .titlewrapper,

191.header-inner .Header .descriptionwrapper {

192padding-left: 30px;

193padding-right: 30px;

194}

195.Header h1 {

Priority 2
Use relative rather than absolute units in CSS property values.
Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users, and a lot of people over 50, increase the browser default font size to make text easier to read. Absolute units ignore this user choice. Relative units like EM and percentages "stretch" according to the screen size and/or user's preferred font size, and work on a large range of devices.

196font: normal normal 24px Arial, Tahoma, Helvetica, FreeSans, sans-serif;

Priority 3
The text-shadow CSS property is not supported by Internet Explorer 9, Firefox 3.0 and BlackBerry 5.

197text-shadow: 1px 1px 3px rgba(0, 0, 0, 0.3);

198}

199.Header h1 a {

200color: #ffffff;

201}

202.Header .description {

203font-size: 90%;

204}

205/* Tabs

206----------------------------------------------- */

207.tabs-inner {

208margin: .5em 0 0;

209padding: 0;

210}

211.tabs-inner .section {

212margin: 0;

213}

214.tabs-inner .widget ul {

215padding: 0;

216background: #f1f1f1 url(https://resources.blogblog.com/blogblog/data/1kt/transparent/tabs_gradient_shade.png) repeat scroll bottom;

Priority 6
Property -moz-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 217 CSS Validation

217-moz-border-radius: 10px;

Priority 6
Property -webkit-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 218 CSS Validation

218-webkit-border-radius: 10px;

Priority 6
Property -goog-ms-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 219 CSS Validation

219-goog-ms-border-radius: 10px;

Priority 3
CSS property border-radius is not supported by IE8 or earlier.
No rounded corners will be displayed on old versions of Internet Explorer.

220border-radius: 10px;

221}

222.tabs-inner .widget li {

223border: none;

224}

225.tabs-inner .widget li a {

226display: inline-block;

227padding: .5em 1em;

228margin-right: 0;

229color: #992211;

Priority 2
Use relative rather than absolute units in CSS property values.
Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users, and a lot of people over 50, increase the browser default font size to make text easier to read. Absolute units ignore this user choice. Relative units like EM and percentages "stretch" according to the screen size and/or user's preferred font size, and work on a large range of devices.

230font: normal normal 15px Arial, Tahoma, Helvetica, FreeSans, sans-serif;

Priority 6
Property -moz-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 231 CSS Validation

231-moz-border-radius: 0 0 0 0;

Priority 6
Property -webkit-border-top-left-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 232 CSS Validation

232-webkit-border-top-left-radius: 0;

Priority 6
Property -webkit-border-top-right-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 233 CSS Validation

233-webkit-border-top-right-radius: 0;

Priority 6
Property -goog-ms-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 234 CSS Validation

234-goog-ms-border-radius: 0 0 0 0;

235border-radius: 0 0 0 0;

236background: transparent none no-repeat scroll top left;

237border-right: 1px solid #c7c7c7;

238}

239.tabs-inner .widget li:first-child a {

240padding-left: 1.25em;

Priority 6
Property -moz-border-radius-topleft is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 241 CSS Validation

241-moz-border-radius-topleft: 10px;

Priority 6
Property -moz-border-radius-bottomleft is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 242 CSS Validation

242-moz-border-radius-bottomleft: 10px;

Priority 6
Property -webkit-border-top-left-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 243 CSS Validation

243-webkit-border-top-left-radius: 10px;

Priority 6
Property -webkit-border-bottom-left-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 244 CSS Validation

244-webkit-border-bottom-left-radius: 10px;

Priority 6
Property -goog-ms-border-top-left-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 245 CSS Validation

245-goog-ms-border-top-left-radius: 10px;

Priority 6
Property -goog-ms-border-bottom-left-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 246 CSS Validation

246-goog-ms-border-bottom-left-radius: 10px;

247border-top-left-radius: 10px;

248border-bottom-left-radius: 10px;

249}

250.tabs-inner .widget li.selected a,

251.tabs-inner .widget li a:hover {

252position: relative;

253z-index: 1;

254background: #ffffff url(https://resources.blogblog.com/blogblog/data/1kt/transparent/tabs_gradient_shade.png) repeat scroll bottom;

255color: #000000;

Priority 6
Property -moz-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 256 CSS Validation

256-moz-box-shadow: 0 0 0 rgba(0, 0, 0, .15);

Priority 6
Property -webkit-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 257 CSS Validation

257-webkit-box-shadow: 0 0 0 rgba(0, 0, 0, .15);

Priority 6
Property -goog-ms-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 258 CSS Validation

258-goog-ms-box-shadow: 0 0 0 rgba(0, 0, 0, .15);

Priority 3
The box-shadow CSS property is not supported in Internet Explorer 8 and Safari 5.0 or earlier.
Boxes will display without a shadow in old versions of Internet Explorer and Safari.

259box-shadow: 0 0 0 rgba(0, 0, 0, .15);

260}

261/* Headings

262----------------------------------------------- */

263h2 {

Priority 2
Use relative rather than absolute units in CSS property values.
Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users, and a lot of people over 50, increase the browser default font size to make text easier to read. Absolute units ignore this user choice. Relative units like EM and percentages "stretch" according to the screen size and/or user's preferred font size, and work on a large range of devices.

264font: bold normal 13px Arial, Tahoma, Helvetica, FreeSans, sans-serif;

265text-transform: uppercase;

266color: #4d4d4d;

267margin: .5em 0;

268}

269/* Main

270----------------------------------------------- */

271.main-outer {

272background: transparent none repeat scroll top center;

Priority 6
Property -moz-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 273 CSS Validation

273-moz-border-radius: 0 0 0 0;

Priority 6
Property -webkit-border-top-left-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 274 CSS Validation

274-webkit-border-top-left-radius: 0;

Priority 6
Property -webkit-border-top-right-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 275 CSS Validation

275-webkit-border-top-right-radius: 0;

Priority 6
Property -webkit-border-bottom-left-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 276 CSS Validation

276-webkit-border-bottom-left-radius: 0;

Priority 6
Property -webkit-border-bottom-right-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 277 CSS Validation

277-webkit-border-bottom-right-radius: 0;

Priority 6
Property -goog-ms-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 278 CSS Validation

278-goog-ms-border-radius: 0 0 0 0;

279border-radius: 0 0 0 0;

Priority 6
Property -moz-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 280 CSS Validation

280-moz-box-shadow: 0 0 0 rgba(0, 0, 0, .15);

Priority 6
Property -webkit-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 281 CSS Validation

281-webkit-box-shadow: 0 0 0 rgba(0, 0, 0, .15);

Priority 6
Property -goog-ms-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 282 CSS Validation

282-goog-ms-box-shadow: 0 0 0 rgba(0, 0, 0, .15);

Priority 3
The box-shadow CSS property is not supported in Internet Explorer 8 and Safari 5.0 or earlier.
Boxes will display without a shadow in old versions of Internet Explorer and Safari.

283box-shadow: 0 0 0 rgba(0, 0, 0, .15);

284}

285.main-inner {

286padding: 15px 5px 20px;

287}

288.main-inner .column-center-inner {

289padding: 0 0;

290}

291.main-inner .column-left-inner {

292padding-left: 0;

293}

294.main-inner .column-right-inner {

295padding-right: 0;

296}

297/* Posts

298----------------------------------------------- */

299h3.post-title {

300margin: 0;

Priority 2
Use relative rather than absolute units in CSS property values.
Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users, and a lot of people over 50, increase the browser default font size to make text easier to read. Absolute units ignore this user choice. Relative units like EM and percentages "stretch" according to the screen size and/or user's preferred font size, and work on a large range of devices.

301font: normal normal 18px Arial, Tahoma, Helvetica, FreeSans, sans-serif;

302}

303.comments h4 {

304margin: 1em 0 0;

Priority 2
Use relative rather than absolute units in CSS property values.
Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users, and a lot of people over 50, increase the browser default font size to make text easier to read. Absolute units ignore this user choice. Relative units like EM and percentages "stretch" according to the screen size and/or user's preferred font size, and work on a large range of devices.

305font: normal normal 18px Arial, Tahoma, Helvetica, FreeSans, sans-serif;

306}

307.date-header span {

308color: #000000;

309}

310.post-outer {

311background-color: #ffffff;

312border: solid 1px #d8d8d8;

Priority 6
Property -moz-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 313 CSS Validation

313-moz-border-radius: 10px;

Priority 6
Property -webkit-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 314 CSS Validation

314-webkit-border-radius: 10px;

Priority 3
CSS property border-radius is not supported by IE8 or earlier.
No rounded corners will be displayed on old versions of Internet Explorer.

315border-radius: 10px;

Priority 6
Property -goog-ms-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 316 CSS Validation

316-goog-ms-border-radius: 10px;

317padding: 15px 20px;

318margin: 0 -20px 20px;

319}

320.post-body {

321line-height: 1.4;

322font-size: 110%;

323position: relative;

324}

325.post-header {

326margin: 0 0 1.5em;

327color: #8f8f8f;

328line-height: 1.6;

329}

330.post-footer {

331margin: .5em 0 0;

332color: #8f8f8f;

333line-height: 1.6;

334}

335#blog-pager {

336font-size: 140%

337}

338#comments .comment-author {

339padding-top: 1.5em;

340border-top: dashed 1px #ccc;

341border-top: dashed 1px rgba(128, 128, 128, .5);

342background-position: 0 1.5em;

343}

344#comments .comment-author:first-child {

345padding-top: 0;

346border-top: none;

347}

348.avatar-image-container {

349margin: .2em 0 0;

350}

351/* Comments

352----------------------------------------------- */

353.comments .comments-content .icon.blog-author {

354background-repeat: no-repeat;

355background-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAASCAYAAABWzo5XAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEgAACxIB0t1+/AAAAAd0SU1FB9sLFwMeCjjhcOMAAAD+SURBVDjLtZSvTgNBEIe/WRRnm3U8RC1neQdsm1zSBIU9VVF1FkUguQQsD9ITmD7ECZIJSE4OZo9stoVjC/zc7ky+zH9hXwVwDpTAWWLrgS3QAe8AZgaAJI5zYAmc8r0G4AHYHQKVwII8PZrZFsBFkeRCABYiMh9BRUhnSkPTNCtVXYXURi1FpBDgArj8QU1eVXUzfnjv7yP7kwu1mYrkWlU33vs1QNu2qU8pwN0UpKoqokjWwCztrMuBhEhmh8bD5UDqur75asbcX0BGUB9/HAMB+r32hznJgXy2v0sGLBcyAJ1EK3LFcbo1s91JeLwAbwGYu7TP/3ZGfnXYPgAVNngtqatUNgAAAABJRU5ErkJggg==);

356}

357.comments .comments-content .loadmore a {

358border-top: 1px solid #cc0000;

359border-bottom: 1px solid #cc0000;

360}

361.comments .continue {

362border-top: 2px solid #cc0000;

363}

364/* Widgets

365----------------------------------------------- */

366.widget ul, .widget #ArchiveList ul.flat {

367padding: 0;

368list-style: none;

369}

370.widget ul li, .widget #ArchiveList ul.flat li {

371border-top: dashed 1px #ccc;

372border-top: dashed 1px rgba(128, 128, 128, .5);

373}

374.widget ul li:first-child, .widget #ArchiveList ul.flat li:first-child {

375border-top: none;

376}

377.widget .post-body ul {

378list-style: disc;

379}

380.widget .post-body ul li {

381border: none;

382}

383/* Footer

384----------------------------------------------- */

385.footer-outer {

386color:#eaeaea;

387background: transparent url(https://resources.blogblog.com/blogblog/data/1kt/transparent/black50.png) repeat scroll top left;

Priority 6
Property -moz-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 388 CSS Validation

388-moz-border-radius: 10px 10px 10px 10px;

Priority 6
Property -webkit-border-top-left-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 389 CSS Validation

389-webkit-border-top-left-radius: 10px;

Priority 6
Property -webkit-border-top-right-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 390 CSS Validation

390-webkit-border-top-right-radius: 10px;

Priority 6
Property -webkit-border-bottom-left-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 391 CSS Validation

391-webkit-border-bottom-left-radius: 10px;

Priority 6
Property -webkit-border-bottom-right-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 392 CSS Validation

392-webkit-border-bottom-right-radius: 10px;

Priority 6
Property -goog-ms-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 393 CSS Validation

393-goog-ms-border-radius: 10px 10px 10px 10px;

Priority 3
CSS property border-radius is not supported by IE8 or earlier.
No rounded corners will be displayed on old versions of Internet Explorer.

394border-radius: 10px 10px 10px 10px;

Priority 6
Property -moz-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 395 CSS Validation

395-moz-box-shadow: 0 0 0 rgba(0, 0, 0, .15);

Priority 6
Property -webkit-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 396 CSS Validation

396-webkit-box-shadow: 0 0 0 rgba(0, 0, 0, .15);

Priority 6
Property -goog-ms-box-shadow is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 397 CSS Validation

397-goog-ms-box-shadow: 0 0 0 rgba(0, 0, 0, .15);

Priority 3
The box-shadow CSS property is not supported in Internet Explorer 8 and Safari 5.0 or earlier.
Boxes will display without a shadow in old versions of Internet Explorer and Safari.

398box-shadow: 0 0 0 rgba(0, 0, 0, .15);

399}

400.footer-inner {

401padding: 10px 5px 20px;

402}

403.footer-outer a {

404color: #f8d5ff;

405}

406.footer-outer a:visited {

407color: #be90c7;

408}

409.footer-outer a:hover {

410color: #ffffff;

411}

412.footer-outer .widget h2 {

413color: #b5b5b5;

414}

415/* Mobile

416----------------------------------------------- */

417html body.mobile {

418height: auto;

419}

420html body.mobile {

421min-height: 480px;

422background-size: 100% auto;

423}

424.mobile .body-fauxcolumn-outer {

425background: transparent none repeat scroll top left;

426}

427html .mobile .mobile-date-outer, html .mobile .blog-pager {

428border-bottom: none;

429background: transparent none repeat scroll top center;

430margin-bottom: 10px;

431}

432.mobile .date-outer {

433background: transparent none repeat scroll top center;

434}

435.mobile .header-outer, .mobile .main-outer,

436.mobile .post-outer, .mobile .footer-outer {

Priority 6
Property -moz-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 437 CSS Validation

437-moz-border-radius: 0;

Priority 6
Property -webkit-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 438 CSS Validation

438-webkit-border-radius: 0;

Priority 6
Property -goog-ms-border-radius is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 439 CSS Validation

439-goog-ms-border-radius: 0;

440border-radius: 0;

441}

442.mobile .content-outer,

443.mobile .main-outer,

444.mobile .post-outer {

445background: inherit;

446border: none;

447}

448.mobile .content-outer {

449font-size: 100%;

450}

451.mobile-link-button {

452background-color: #094c8c;

453}

454.mobile-link-button a:link, .mobile-link-button a:visited {

455color: #ffffff;

456}

457.mobile-index-contents {

458color: #000000;

459}

460.mobile .tabs-inner .PageList .widget-content {

461background: #ffffff url(https://resources.blogblog.com/blogblog/data/1kt/transparent/tabs_gradient_shade.png) repeat scroll bottom;

462color: #000000;

463}

464.mobile .tabs-inner .PageList .widget-content .pagelist-arrow {

465border-left: 1px solid #c7c7c7;

466}

467

468--></style>

469<style id='template-skin-1' type='text/css'><!--

470body {

471min-width: 900px;

472}

473.content-outer, .content-fauxcolumn-outer, .region-inner {

474min-width: 900px;

475max-width: 900px;

Priority 2
The CSS underscore filter hack no longer works in IE7 or later.
Underscored property names are treated as custom properties in IE7. Conditional comments are a fully supported, standards-compliant alternative.
Priority 6
Property _width is vendor specific.
Properties prefixed by a dash or underscore are vendor specific and only work on one browser engine.
Line 476 CSS Validation

476_width: 900px;

477}

478.main-inner .columns {

479padding-left: 0px;

480padding-right: 250px;

481}

482.main-inner .fauxcolumn-center-outer {

483left: 0px;

484right: 250px;

485/* IE6 does not respect left and right together */

Priority 1
CSS expressions are not supported in IE8 and IE9 standards mode.
CSS property values like height: expression( 3*4 ); are only supported by IE6, IE7 and IE8 compatibility mode, They are not supported in other browsers or IE8 and IE9 standards mode.
Priority 1
CSS expressions are only supported by Internet Explorer.
CSS property values like height: expression( 3*4 ); are only supported by IE6 and IE7. They are not supported in other browsers or IE8 standards mode.
Priority 1
CSS Validation Error.
Line 486 CSS Validation

486_width: expression(this.parentNode.offsetWidth -

487parseInt("0px") -

488parseInt("250px") + 'px');

489}

490.main-inner .fauxcolumn-left-outer {

491width: 0px;

492}

493.main-inner .fauxcolumn-right-outer {

494width: 250px;

495}

496.main-inner .column-left-outer {

497width: 0px;

498right: 100%;

499margin-left: -0px;

500}

501.main-inner .column-right-outer {

502width: 250px;

503margin-right: -250px;

504}

505#layout {

506min-width: 0;

507}

508#layout .content-outer {

509min-width: 0;

510width: 800px;

511}

512#layout .region-inner {

513min-width: 0;

514width: auto;

515}

516body#layout div.add_widget {

517padding: 8px;

518}

519body#layout div.add_widget a {

520margin-left: 32px;

521}

522--></style>

523<style>

524 body {background-image:

Priority 2
Use background images sparingly and make sure they are simple, especially behind text.
Background images can make it difficult for users to read foreground text. A single, large, complex background image (including a picture) can substantially slow page download rates.

url(\/\/themes.googleusercontent.com\/image?id=1fPzKKjY9pDchHIeFXfLO2zY1SYfTku0PLrkb-Aiu7meqodh01WKnpNCHAuTcBrMZaM6D);}

525

526@media (max-width: 200px) { body {background-image:url(\/\/themes.googleusercontent.com\/image?id=1fPzKKjY9pDchHIeFXfLO2zY1SYfTku0PLrkb-Aiu7meqodh01WKnpNCHAuTcBrMZaM6D&options=w200);}}

527@media (max-width: 400px) and (min-width: 201px) { body {background-image:url(\/\/themes.googleusercontent.com\/image?id=1fPzKKjY9pDchHIeFXfLO2zY1SYfTku0PLrkb-Aiu7meqodh01WKnpNCHAuTcBrMZaM6D&options=w400);}}

528@media (max-width: 800px) and (min-width: 401px) { body {background-image:url(\/\/themes.googleusercontent.com\/image?id=1fPzKKjY9pDchHIeFXfLO2zY1SYfTku0PLrkb-Aiu7meqodh01WKnpNCHAuTcBrMZaM6D&options=w800);}}

529@media (max-width: 1200px) and (min-width: 801px) { body {background-image:url(\/\/themes.googleusercontent.com\/image?id=1fPzKKjY9pDchHIeFXfLO2zY1SYfTku0PLrkb-Aiu7meqodh01WKnpNCHAuTcBrMZaM6D&options=w1200);}}

530/* Last tag covers anything over one higher than the previous max-size cap. */

531@media (min-width: 1201px) { body {background-image:url(\/\/themes.googleusercontent.com\/image?id=1fPzKKjY9pDchHIeFXfLO2zY1SYfTku0PLrkb-Aiu7meqodh01WKnpNCHAuTcBrMZaM6D&options=w1600);}}

532 </style>

Priority 1
Bad value for attribute 'media'. Bad value 'none'. Syntax error in media query
Line 533 HTML5

533<link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=8956464986740803789&amp;zx=4bb86c54-0efb-4036-a7bf-720d1d400fa6' media='none' onload='if(media!=&#39;all&#39;)media=&#39;all&#39;' rel='stylesheet'/><noscript><link href='https://www.blogger.com/dyn-css/authorization.css?targetBlogID=8956464986740803789&amp;zx=4bb86c54-0efb-4036-a7bf-720d1d400fa6' rel='stylesheet'/></noscript>

534</head>

Priority 1
This page has no H1 element, which violates Bing webmaster guidelines.
Add an H1 element just before the main content describing the page.
Line 535 Bing

535<body class='loading'>

Priority 1
Attribute ':name' not allowed on element.
Line 536 HTML5

536<div class='navbar section' id='navbar' name='Панель навигации'><div class='widget Navbar' data-version='1' id='Navbar1'><script type="text/javascript">

537 function setAttributeOnload(object, attribute, val) {

538 if(window.addEventListener) {

539 window.addEventListener('load',

540 function(){ object[attribute] = val; }, false);

541 } else {

542 window.attachEvent('onload', function(){ object[attribute] = val; });

543 }

544 }

545 </script>

546<div id="navbar-iframe-container"></div>

547<script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script>

548<script type="text/javascript">

549 gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() {

550 if (gapi.iframes && gapi.iframes.getContext) {

551 gapi.iframes.getContext().openChild({

552 url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d8956464986740803789\x26blogName\x3d%D0%92%D0%B5%D0%BA%D1%82%D0%BE%D1%80%D0%BD%D0%B0%D1%8F+%D1%82%D0%B5%D0%BE%D1%80%D0%B8%D1%8F+%D1%81%D0%BE%D1%86%D0%B8%D0%B0%D0%BB%D1%8C%D0%BD%D0%BE%D0%B9+%D1%80%D0%B5%D0%B2%D0%BE%D0%BB%D1%8E%D1%86%D0%B8%D0%B8\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dLIGHT\x26layoutType\x3dLAYOUTS\x26searchRoot\x3dhttps://vector-rev.blogspot.com/search\x26blogLocale\x3dru\x26v\x3d2\x26homepageUrl\x3dhttps://vector-rev.blogspot.com/\x26targetPostID\x3d4865024095207574136\x26blogPostOrPageUrl\x3dhttps://vector-rev.blogspot.com/2017/07/blog-post_16.html\x26vt\x3d-7067044508715962597',

553 where: document.getElementById("navbar-iframe-container"),

554 id: "navbar-iframe"

555 });

556 }

557 });

558 </script><script type="text/javascript">

559(function() {

560var script = document.createElement('script');

561script.type = 'text/javascript';

562script.src = '//pagead2.googlesyndication.com/pagead/js/google_top_exp.js';

563var head = document.getElementsByTagName('head')[0];

564if (head) {

565head.appendChild(script);

566}})();

567</script>

568</div></div>

569<div class='body-fauxcolumns'>

570<div class='fauxcolumn-outer body-fauxcolumn-outer'>

571<div class='cap-top'>

572<div class='cap-left'></div>

573<div class='cap-right'></div>

574</div>

575<div class='fauxborder-left'>

576<div class='fauxborder-right'></div>

577<div class='fauxcolumn-inner'>

578</div>

579</div>

580<div class='cap-bottom'>

581<div class='cap-left'></div>

582<div class='cap-right'></div>

583</div>

584</div>

585</div>

586<div class='content'>

587<div class='content-fauxcolumns'>

588<div class='fauxcolumn-outer content-fauxcolumn-outer'>

589<div class='cap-top'>

590<div class='cap-left'></div>

591<div class='cap-right'></div>

592</div>

593<div class='fauxborder-left'>

594<div class='fauxborder-right'></div>

595<div class='fauxcolumn-inner'>

596</div>

597</div>

598<div class='cap-bottom'>

599<div class='cap-left'></div>

600<div class='cap-right'></div>

601</div>

602</div>

603</div>

604<div class='content-outer'>

605<div class='content-cap-top cap-top'>

606<div class='cap-left'></div>

607<div class='cap-right'></div>

608</div>

609<div class='fauxborder-left content-fauxborder-left'>

610<div class='fauxborder-right content-fauxborder-right'></div>

611<div class='content-inner'>

612<header>

613<div class='header-outer'>

614<div class='header-cap-top cap-top'>

615<div class='cap-left'></div>

616<div class='cap-right'></div>

617</div>

618<div class='fauxborder-left header-fauxborder-left'>

619<div class='fauxborder-right header-fauxborder-right'></div>

620<div class='region-inner header-inner'>

Priority 1
Attribute ':name' not allowed on element.
Line 621 HTML5

621<div class='header section' id='header' name='Заголовок'><div class='widget Header' data-version='1' id='Header1'>

622<div id='header-inner'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

623<a href='https://vector-rev.blogspot.is/' style='display: block'>

Priority 2
The IMG WIDTH and HEIGHT attributes don't match the actual image size. This means the image will be scaled or distorted. Image https://2.bp.blogspot.com/-ear2xsVtqJE/WVOIVeIj0hI/AAAAAAAACzY/0qUxg1HPk9g0i8wPxx5Z5Ri0M1Y-ZJWFACK4BGAYYCw/s1600/cover_1_m.jpg actual dimensions: 640 x 390 pixels.
Line 624 W3C
Priority 1
Bad value for attribute 'height'. Bad value '390px; '. Expected a digit but saw instead.
Line 624 HTML5
Priority 1
Bad value for attribute 'width'. Bad value '640px; '. Expected a digit but saw instead.
Line 624 HTML5

624<img alt="Векторная теория социальной революции" height="390px; " id="Header1_headerimg" src="//2.bp.blogspot.com/-ear2xsVtqJE/WVOIVeIj0hI/AAAAAAAACzY/0qUxg1HPk9g0i8wPxx5Z5Ri0M1Y-ZJWFACK4BGAYYCw/s1600/cover_1_m.jpg" style="display: block" width="640px; ">

625</a>

626<div class='descriptionwrapper'>

627<p class='description'><span>Новое определение социальной революции, как перемещения государства в пространстве политических идей по вектору, направленному от простых, архаичных идей, к более сложным, прогрессивным. Движущие силы революции и генетический базис человеческой пассионарности. Математическая модель народного восстания (бунта). Контуры новой социально-экономической формации, в которой устраняется эксплуатация человека человеком, человека государством и трудящихся финансовой олигархией.</span></p>

628</div>

629</div>

630</div></div>

631</div>

632</div>

633<div class='header-cap-bottom cap-bottom'>

634<div class='cap-left'></div>

635<div class='cap-right'></div>

636</div>

637</div>

638</header>

639<div class='tabs-outer'>

640<div class='tabs-cap-top cap-top'>

641<div class='cap-left'></div>

642<div class='cap-right'></div>

643</div>

644<div class='fauxborder-left tabs-fauxborder-left'>

645<div class='fauxborder-right tabs-fauxborder-right'></div>

646<div class='region-inner tabs-inner'>

Priority 1
Attribute ':name' not allowed on element.
Line 647 HTML5

647<div class='tabs section' id='crosscol' name='Поперечный столбец'><div class='widget HTML' data-version='1' id='HTML2'>

648<h2 class='title'>banners</h2>

649<div class='widget-content'>

650</div>

651<div class='clear'></div>

652<span class='widget-item-control'>

653<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

654<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=crosscol' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML2"));' target='configHTML2' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

655<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

656</a>

657</span>

658</span>

659<div class='clear'></div>

660</div></div>

Priority 1
Attribute ':name' not allowed on element.
Line 661 HTML5

661<div class='tabs no-items section' id='crosscol-overflow' name='Cross-Column 2'></div>

662</div>

663</div>

664<div class='tabs-cap-bottom cap-bottom'>

665<div class='cap-left'></div>

666<div class='cap-right'></div>

667</div>

668</div>

669<div class='main-outer'>

670<div class='main-cap-top cap-top'>

671<div class='cap-left'></div>

672<div class='cap-right'></div>

673</div>

674<div class='fauxborder-left main-fauxborder-left'>

675<div class='fauxborder-right main-fauxborder-right'></div>

676<div class='region-inner main-inner'>

677<div class='columns fauxcolumns'>

678<div class='fauxcolumn-outer fauxcolumn-center-outer'>

679<div class='cap-top'>

680<div class='cap-left'></div>

681<div class='cap-right'></div>

682</div>

683<div class='fauxborder-left'>

684<div class='fauxborder-right'></div>

685<div class='fauxcolumn-inner'>

686</div>

687</div>

688<div class='cap-bottom'>

689<div class='cap-left'></div>

690<div class='cap-right'></div>

691</div>

692</div>

693<div class='fauxcolumn-outer fauxcolumn-left-outer'>

694<div class='cap-top'>

695<div class='cap-left'></div>

696<div class='cap-right'></div>

697</div>

698<div class='fauxborder-left'>

699<div class='fauxborder-right'></div>

700<div class='fauxcolumn-inner'>

701</div>

702</div>

703<div class='cap-bottom'>

704<div class='cap-left'></div>

705<div class='cap-right'></div>

706</div>

707</div>

708<div class='fauxcolumn-outer fauxcolumn-right-outer'>

709<div class='cap-top'>

710<div class='cap-left'></div>

711<div class='cap-right'></div>

712</div>

713<div class='fauxborder-left'>

714<div class='fauxborder-right'></div>

715<div class='fauxcolumn-inner'>

716</div>

717</div>

718<div class='cap-bottom'>

719<div class='cap-left'></div>

720<div class='cap-right'></div>

721</div>

722</div>

723<!-- corrects IE6 width calculation -->

724<div class='columns-inner'>

725<div class='column-center-outer'>

726<div class='column-center-inner'>

727<div class='main section' id='main' name='Основной'><div class='widget Blog' data-version='1' id='Blog1'>

728<div class='blog-posts hfeed'>

729

730 <div class="date-outer">

731

732<h2 class='date-header'><span>понедельник, 10 июля 2017 г.</span></h2>

733

734 <div class="date-posts">

735

736<div class='post-outer'>

737<div class='post hentry uncustomized-post-template' itemprop='blogPost' itemscope='itemscope' itemtype='http://schema.org/BlogPosting'>

738<meta content='https://img.youtube.com/vi/kAUS8pav1sw/hqdefault.jpg' itemprop='image_url'/>

739<meta content='8956464986740803789' itemprop='blogId'/>

740<meta content='4865024095207574136' itemprop='postId'/>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>
Priority 2
The 'name' attribute on the 'a' element is obsolete. Consider putting an 'id' attribute on the nearest container instead.
Line 741 HTML5

741<a name='4865024095207574136'></a>

742<h3 class='post-title entry-title' itemprop='name'>

743Читатели книги "Векторная теория социальной революции"

744</h3>

745<div class='post-header'>

746<div class='post-header-line-1'></div>

747</div>

748<div class='post-body entry-content' id='post-body-4865024095207574136' itemprop='description articleBody'>

Priority 1
No TITLE attributes found for the frames on these pages.
Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Without a TITLE some screen readers read out the FRAME filename, which is usually meaningless.

IFRAMEs with no title cause problems in:

  • JAWS 14 and 15 with Firefox (the frame SRC filename is read instead)
  • VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)
Priority 1
The 'frameborder' attribute on the 'iframe' element is obsolete. Use CSS instead.
Line 749 HTML5

749<iframe allowfullscreen="" frameborder="0" height="270" src="https://www.youtube.com/embed/kAUS8pav1sw" width="480"></iframe>

750<div style='clear: both;'></div>

751</div>

752<div class='post-footer'>

753<div class='post-footer-line post-footer-line-1'>

754<span class='post-author vcard'>

755</span>

756<span class='post-timestamp'>

757на

758<meta content='https://vector-rev.blogspot.com/2017/07/blog-post_16.html' itemprop='url'/>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

759<a class='timestamp-link' href='https://vector-rev.blogspot.is/2017/07/blog-post_16.html' rel='bookmark' title='permanent link'><abbr class='published' itemprop='datePublished' title='2017-07-10T22:13:00-07:00'>июля 10, 2017</abbr></a>

760</span>

761<span class='reaction-buttons'>

762</span>

763<span class='post-comment-link'>

764</span>

765<span class='post-backlinks post-comment-link'>

766</span>

767<span class='post-icons'>

768<span class='item-control blog-admin pid-1812335567'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

769<a href='https://www.blogger.com/post-edit.g?blogID=8956464986740803789&postID=4865024095207574136&from=pencil' title='Изменить сообщение'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

770<img alt='' class='icon-action' height='18' src='https://resources.blogblog.com/img/icon18_edit_allbkg.gif' width='18'/>

771</a>

772</span>

773</span>

774<div class='post-share-buttons goog-inline-block'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

775<a class='goog-inline-block share-button sb-email' href='https://www.blogger.com/share-post.g?blogID=8956464986740803789&postID=4865024095207574136&target=email' target='_blank' title='Отправить по электронной почте'><span class='share-button-link-text'>Отправить по электронной почте</span></a><a class='goog-inline-block share-button sb-blog' href='https://www.blogger.com/share-post.g?blogID=8956464986740803789&postID=4865024095207574136&target=blog' onclick='window.open(this.href, "_blank", "height=270,width=475"); return false;' target='_blank' title='Написать об этом в блоге'><span class='share-button-link-text'>Написать об этом в блоге</span></a><a class='goog-inline-block share-button sb-twitter' href='https://www.blogger.com/share-post.g?blogID=8956464986740803789&postID=4865024095207574136&target=twitter' target='_blank' title='Опубликовать в Twitter'><span class='share-button-link-text'>Опубликовать в Twitter</span></a><a class='goog-inline-block share-button sb-facebook' href='https://www.blogger.com/share-post.g?blogID=8956464986740803789&postID=4865024095207574136&target=facebook' onclick='window.open(this.href, "_blank", "height=430,width=640"); return false;' target='_blank' title='Опубликовать в Facebook'><span class='share-button-link-text'>Опубликовать в Facebook</span></a><a class='goog-inline-block share-button sb-pinterest' href='https://www.blogger.com/share-post.g?blogID=8956464986740803789&postID=4865024095207574136&target=pinterest' target='_blank' title='Поделиться в Pinterest'><span class='share-button-link-text'>Поделиться в Pinterest</span></a><div class='goog-inline-block google-plus-share-container'>

Priority 1
Self-closing syntax ('/>') used on a non-void HTML element. Ignoring the slash and treating as a start tag.
Line 775 HTML5

<g:plusone source='blogger:blog:plusone' href='http://vector-rev.blogspot.com/2017/07/blog-post_16.html' size='medium' width='300' annotation='inline'/>

Priority 1
Unclosed element 'g:plusone'.
Line 775 HTML5
Priority 1
End tag 'div' seen, but there were open elements.
Line 775 HTML5
Priority 1
This page has markup errors, causing screen readers to miss content.
Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.

</div>

776</div>

777</div>

778<div class='post-footer-line post-footer-line-2'>

779<span class='post-labels'>

780</span>

781</div>

782<div class='post-footer-line post-footer-line-3'>

783<span class='post-location'>

784</span>

785</div>

786</div>

787</div>

788<div class='comments' id='comments'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>
Priority 2
The 'name' attribute on the 'a' element is obsolete. Consider putting an 'id' attribute on the nearest container instead.
Line 789 HTML5

789<a name='comments'></a>

790<h4>Комментариев нет:</h4>

791<div id='Blog1_comments-block-wrapper'>

792<dl class='avatar-comment-indent' id='comments-block'>

793</dl>

794</div>

795<p class='comment-footer'>

796<div class='comment-form'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>
Priority 2
The 'name' attribute on the 'a' element is obsolete. Consider putting an 'id' attribute on the nearest container instead.
Line 797 HTML5

797<a name='comment-form'></a>

798<h4 id='comment-post-message'>Отправить комментарий</h4>

799<p>

800</p>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)

801<a href='https://www.blogger.com/comment-iframe.g?blogID=8956464986740803789&postID=4865024095207574136' id='comment-editor-src'></a>

Priority 1
No TITLE attributes found for the frames on these pages.
Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Without a TITLE some screen readers read out the FRAME filename, which is usually meaningless.

IFRAMEs with no title cause problems in:

  • JAWS 14 and 15 with Firefox (the frame SRC filename is read instead)
  • VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)
Priority 1
Internet Explorer, Chrome and Firefox display a security warning when a secure https:// web page includes http:// content.
In IE8 and Firefox 23 onwards, the default option is not to display the http:// content. To fix this: use relative URL paths `../images/file.png`; or full URL paths `/images/file.png`; or absolute https URLs `https://example.com/images/file.png`.
Priority 1
This link is broken. The SRC or HREF is an empty string. Link: URL is empty.
HREF="" or SRC="" can cause unexpected effects such as traffic spikes or cookie corruption, and causes JavaScript error events to fire on Firefox.
Line 802 Broken Link
Priority 1
The 'allowtransparency' attribute on the 'iframe' element is obsolete. Use CSS instead.
Line 802 HTML5
Priority 1
The 'frameborder' attribute on the 'iframe' element is obsolete. Use CSS instead.
Line 802 HTML5

802<iframe allowtransparency='true' class='blogger-iframe-colorize blogger-comment-from-post' frameborder='0' height='410px' id='comment-editor' name='comment-editor' src='' width='100%'></iframe>

803<script src='https://www.blogger.com/static/v1/jsbin/569042235-comment_from_post_iframe.js' type='text/javascript'></script>

804<script type='text/javascript'>

805 BLOG_CMT_createIframe('https://www.blogger.com/rpc_relay.html');

806 </script>

807</div>

Priority 1
No 'p' element in scope but a 'p' end tag seen.
Line 808 HTML5

808</p>

809<div id='backlinks-container'>

810<div id='Blog1_backlinks-container'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>
Priority 2
The 'name' attribute on the 'a' element is obsolete. Consider putting an 'id' attribute on the nearest container instead.
Line 811 HTML5

811<a name='links'></a><h4><!--Can't find substitution for tag [post.backlinksLabel]--></h4>

812<p class='comment-footer'>

Priority 1
This link is broken. The SRC or HREF is an empty string. Link: URL is empty.
HREF="" or SRC="" can cause unexpected effects such as traffic spikes or cookie corruption, and causes JavaScript error events to fire on Firefox.
Line 813 Broken Link
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

813<a class='comment-link' href='' id='Blog1_backlinks-create-link' target='_blank'><!--Can't find substitution for tag [post.createLinkLabel]--></a>

814</p>

815</div>

816</div>

817</div>

818</div>

819<div class='inline-ad'>

820</div>

821

822 </div></div>

823

824</div>

825<div class='blog-pager' id='blog-pager'>

826<span id='blog-pager-older-link'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

827<a class='blog-pager-older-link' href='https://vector-rev.blogspot.is/2017/07/blog-post_82.html' id='Blog1_blog-pager-older-link' title='Предыдущее'>Предыдущее</a>

828</span>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

829<a class='home-link' href='https://vector-rev.blogspot.is/'>Главная страница</a>

830</div>

831<div class='clear'></div>

832<div class='post-feeds'>

833<div class='feed-links'>

834Подписаться на:

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

835<a class='feed-link' href='https://vector-rev.blogspot.com/feeds/4865024095207574136/comments/default' target='_blank' type='application/atom+xml'>Комментарии к сообщению (Atom)</a>

836</div>

837</div>

838<script type='text/javascript'>

839 window.___gcfg = { 'lang': 'ru' };

840 </script>

841</div><div class='widget PopularPosts' data-version='1' id='PopularPosts1'>

842<div class='widget-content popular-posts'>

843<ul>

844<li>

845<div class='item-content'>

846<div class='item-thumbnail'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

847<a href='https://vector-rev.blogspot.is/2017/06/blog-post_29.html' target='_blank'>

Priority 2
Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.
This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.
Priority 2
The 'border' attribute on the 'img' element is obsolete. Consider specifying 'img { border: 0; }' in CSS instead.
Line 848 HTML5

848<img alt='' border='0' src='https://4.bp.blogspot.com/-qR0mrav4MsM/WVTl6kGbQ8I/AAAAAAAACzk/OSRRcclNSpM99VkgY7jgHHvVdIuS4YifQCLcBGAs/w72-h72-p-k-no-nu/Korjev_GM-Podnimayuschiy-znamya.jpg'/>

849</a>

850</div>

851<div class='item-title'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/06/blog-post_29.html'>Факторы угнетения, факторы бунта</a></div>

852<div class='item-snippet'> Извлечение из главы 4 &quot;Угнетение и принуждение&quot;.&#160; Из книги Егоров С.Н., Цыпленков П.В. &#160; Векторная теория социальной революц...</div>

853</div>

854<div style='clear: both;'></div>

855</li>

856<li>

857<div class='item-content'>

858<div class='item-thumbnail'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

859<a href='https://vector-rev.blogspot.is/2017/07/blog-post_6.html' target='_blank'>

Priority 2
Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.
This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.
Priority 2
The 'border' attribute on the 'img' element is obsolete. Consider specifying 'img { border: 0; }' in CSS instead.
Line 860 HTML5

860<img alt='' border='0' src='https://1.bp.blogspot.com/-wUe56Rx5Wio/WV5Br4dcwyI/AAAAAAAAC2Q/gL1odmXIaOwkEn1ecdIOjsWaWNqLtO4CQCLcBGAs/w72-h72-p-k-no-nu/bastille-1.jpg'/>

861</a>

862</div>

863<div class='item-title'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_6.html'>Что же такое революция?</a></div>

864<div class='item-snippet'> Что такое революция ? Революции, революционные движения и идеологии &#8211; начиная с 1917 г. и заканчивая современными революциями в странах п...</div>

865</div>

866<div style='clear: both;'></div>

867</li>

868<li>

869<div class='item-content'>

870<div class='item-thumbnail'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

871<a href='https://vector-rev.blogspot.is/2017/07/blog-post.html' target='_blank'>

Priority 2
Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.
This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.
Priority 2
The 'border' attribute on the 'img' element is obsolete. Consider specifying 'img { border: 0; }' in CSS instead.
Line 872 HTML5

872<img alt='' border='0' src='https://1.bp.blogspot.com/-zM4PRN1yZw0/WVjq8tiylKI/AAAAAAAAC0I/sVI6oPTOerwbpj0pe_2HCjZpFgDbZbV-QCLcBGAs/w72-h72-p-k-no-nu/DSC02069.JPG'/>

873</a>

874</div>

875<div class='item-title'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post.html'>Люди, революции и государство</a></div>

876<div class='item-snippet'> Комментарий к книге: Егоров С.Н., Цыпленков П.В. Векторная теория социальной революции . &#8211; СПб.: б.и., 2017. &#8211; 400 с., 38 ил. Журнали...</div>

877</div>

878<div style='clear: both;'></div>

879</li>

880</ul>

881<div class='clear'></div>

882<span class='widget-item-control'>

883<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

884<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&sectionId=main' onclick='return _WidgetManager._PopupConfig(document.getElementById("PopularPosts1"));' target='configPopularPosts1' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

885<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

886</a>

887</span>

888</span>

889<div class='clear'></div>

890</div>

891</div></div>

892</div>

893</div>

894<div class='column-left-outer'>

895<div class='column-left-inner'>

896<aside>

897</aside>

898</div>

899</div>

900<div class='column-right-outer'>

901<div class='column-right-inner'>

902<aside>

903<div class='sidebar section' id='sidebar-right-1'><div class='widget BlogSearch' data-version='1' id='BlogSearch1'>

904<h2 class='title'>Поиск в блоге</h2>

905<div class='widget-content'>

906<div id='BlogSearch1_form'>

907<form action='https://vector-rev.blogspot.is/search' class='gsc-search-box' target='_top'>

Priority 1
Identify row and column headers in data tables using TH elements, and mark layout tables with role='presentation'.
Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Impact on users:

  • JAWS Reading: Treats tables without TH and ROLE as layout tables if the table contains cells above or below certain pixel sizes. This measurement is affected by browser window size, browser font size, and the browser used.
  • NVDA Reading: Applies a 'layout table' heuristic to tables without TH and ROLE which varies depending on the browser used and on the window size in some circumstances.
  • VoiceOver Safari OSX 10.9 Reading: Uses a sophisticated heuristic on tables without TH and ROLE, which is similar (but not identical) to the heuristic used by NVDA with Firefox.
Priority 1
The 'cellpadding' attribute on the 'table' element is obsolete. Use CSS instead.
Line 908 HTML5
Priority 1
The 'cellspacing' attribute on the 'table' element is obsolete. Use CSS instead.
Line 908 HTML5

908<table cellpadding='0' cellspacing='0' class='gsc-search-box'>

909<tbody>

910<tr>

911<td class='gsc-input'>

912<input autocomplete='off' class='gsc-input' name='q' size='10' title='search' type='text' value=''/>

913</td>

914<td class='gsc-search-button'>

915<input class='gsc-search-button' title='search' type='submit' value='Поиск'/>

916</td>

917</tr>

918</tbody>

919</table>

920</form>

921</div>

922</div>

923<div class='clear'></div>

924<span class='widget-item-control'>

925<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

926<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=BlogSearch&widgetId=BlogSearch1&action=editWidget&sectionId=sidebar-right-1' onclick='return _WidgetManager._PopupConfig(document.getElementById("BlogSearch1"));' target='configBlogSearch1' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

927<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

928</a>

929</span>

930</span>

931<div class='clear'></div>

932</div><div class='widget Profile' data-version='1' id='Profile1'>

933<h2>Авторы</h2>

934<div class='widget-content'>

935<ul>

936<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a class='profile-name-link g-profile' href='https://www.blogger.com/profile/17975942912771403374' style='background-image: url(//www.blogger.com/img/logo-16.png);'>Pavlushka</a></li>

937<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a class='profile-name-link g-profile' href='https://plus.google.com/100556921731621701496' style='background-image: url(//www.google.com/images/icons/ui/gprofile_button-16.png);'>Екатерина Котосонова</a></li>

938<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a class='profile-name-link g-profile' href='https://www.blogger.com/profile/10046873630909223805' style='background-image: url(//www.blogger.com/img/logo-16.png);'>СерБас</a></li>

939<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a class='profile-name-link g-profile' href='https://www.blogger.com/profile/18381431541372619582' style='background-image: url(//www.blogger.com/img/logo-16.png);'>Сергей Павлов</a></li>

940</ul>

941<div class='clear'></div>

942<span class='widget-item-control'>

943<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

944<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=Profile&widgetId=Profile1&action=editWidget&sectionId=sidebar-right-1' onclick='return _WidgetManager._PopupConfig(document.getElementById("Profile1"));' target='configProfile1' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

945<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

946</a>

947</span>

948</span>

949<div class='clear'></div>

950</div>

951</div><div class='widget BlogArchive' data-version='1' id='BlogArchive1'>

952<h2>Архив блога</h2>

953<div class='widget-content'>

954<div id='ArchiveList'>

955<div id='BlogArchive1_ArchiveList'>

956<ul class='hierarchy'>

957<li class='archivedate expanded'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

958<a class='toggle' href='javascript:void(0)'>

959<span class='zippy toggle-open'>

960

961 &#9660;&#160;

962

963</span>

964</a>

965<a class='post-count-link' href='https://vector-rev.blogspot.is/2017/'>

9662017

967</a>

968<span class='post-count' dir='ltr'>(17)</span>

969<ul class='hierarchy'>

970<li class='archivedate collapsed'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

971<a class='toggle' href='javascript:void(0)'>

972<span class='zippy'>

973

974 &#9658;&#160;

975

976</span>

977</a>

978<a class='post-count-link' href='https://vector-rev.blogspot.is/2017/06/'>

979июня 2017

980</a>

981<span class='post-count' dir='ltr'>(6)</span>

982</li>

983</ul>

984<ul class='hierarchy'>

985<li class='archivedate expanded'>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

986<a class='toggle' href='javascript:void(0)'>

987<span class='zippy toggle-open'>

988

989 &#9660;&#160;

990

991</span>

992</a>

993<a class='post-count-link' href='https://vector-rev.blogspot.is/2017/07/'>

994июля 2017

995</a>

996<span class='post-count' dir='ltr'>(11)</span>

997<ul class='posts'>

998<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post.html'>Люди, революции и государство</a></li>

999<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_3.html'>Дан старт проекту сбора средств для издания книги</a></li>

1000<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_4.html'>Нужны ли революциям казни?</a></li>

1001<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_6.html'>Что же такое революция?</a></li>

1002<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_7.html'>Пробная версия книги &quot;Векторная теория социальной ...</a></li>

1003<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_9.html'>Первый шаг сделан</a></li>

1004<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_10.html'>Фрилансизм - это стадия развития общества после ка...</a></li>

1005<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_51.html'>Векторная теория социальной революции. Как создава...</a></li>

1006<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_96.html'>Что такое революция?</a></li>

1007<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_82.html'>Пространство политических идей</a></li>

1008<li>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='https://vector-rev.blogspot.is/2017/07/blog-post_16.html'>Читатели книги &quot;Векторная теория социальной револю...</a></li>

1009</ul>

1010</li>

1011</ul>

1012</li>

1013</ul>

1014</div>

1015</div>

1016<div class='clear'></div>

1017<span class='widget-item-control'>

1018<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

1019<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=BlogArchive&widgetId=BlogArchive1&action=editWidget&sectionId=sidebar-right-1' onclick='return _WidgetManager._PopupConfig(document.getElementById("BlogArchive1"));' target='configBlogArchive1' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

1020<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

1021</a>

1022</span>

1023</span>

1024<div class='clear'></div>

1025</div>

1026</div><div class='widget HTML' data-version='1' id='HTML1'>

1027<div class='widget-content'>

1028<script type="text/javascript" src="//platform-api.sharethis.com/js/sharethis.js#property=5953904f3b4e8e0012f0a63b&amp;product=sticky-share-buttons"></script>

1029<div style="text-align: center">

Priority 1
No TITLE attributes found for the frames on these pages.
Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Without a TITLE some screen readers read out the FRAME filename, which is usually meaningless.

IFRAMEs with no title cause problems in:

  • JAWS 14 and 15 with Firefox (the frame SRC filename is read instead)
  • VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)
Priority 1
The 'frameborder' attribute on the 'iframe' element is obsolete. Use CSS instead.
Line 1029 HTML5

<iframe frameborder="0" width="192" height="240" src="https://widgets.planeta.ru/widgets/affiliate-campaign-widget.html?name=CAMPAIGN_192X240&campaign-id=65268&affiliate-id=0&background=BLACK&font-color=WHITE&share-id=255437"></iframe><br />

1030

1031</div>

1032</div>

1033<div class='clear'></div>

1034<span class='widget-item-control'>

1035<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

1036<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar-right-1' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML1"));' target='configHTML1' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

1037<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

1038</a>

1039</span>

1040</span>

1041<div class='clear'></div>

1042</div><div class='widget FollowByEmail' data-version='1' id='FollowByEmail2'>

1043<h2 class='title'>Новости на Вашу почту</h2>

1044<div class='widget-content'>

1045<div class='follow-by-email-inner'>

1046<form action='https://feedburner.google.com/fb/a/mailverify' method='post' onsubmit='window.open("https://feedburner.google.com/fb/a/mailverify?uri=blogspot/pEcXSD", "popupwindow", "scrollbars=yes,width=550,height=520"); return true' target='popupwindow'>

Priority 1
Identify row and column headers in data tables using TH elements, and mark layout tables with role='presentation'.
Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Impact on users:

  • JAWS Reading: Treats tables without TH and ROLE as layout tables if the table contains cells above or below certain pixel sizes. This measurement is affected by browser window size, browser font size, and the browser used.
  • NVDA Reading: Applies a 'layout table' heuristic to tables without TH and ROLE which varies depending on the browser used and on the window size in some circumstances.
  • VoiceOver Safari OSX 10.9 Reading: Uses a sophisticated heuristic on tables without TH and ROLE, which is similar (but not identical) to the heuristic used by NVDA with Firefox.
Priority 1
The 'width' attribute on the 'table' element is obsolete. Use CSS instead.
Line 1047 HTML5

1047<table width='100%'>

1048<tr>

1049<td>

Priority 1
This form control has no LABEL and no programmatically determined name.

A programmatically determined name allows screen readers to tell the user what the control does. To add a name do one of the following:

  • Use a LABEL element with the FOR attribute set to the ID of the form control
  • Wrap a LABEL element around the form control
  • Add a TITLE attribute
  • Add an ARIA-LABELLEDBY attribute (not supported in all screen readers)
  • Add an ARIA-LABEL attribute (not supported in all screen readers)
Priority 1
This form has fields without LABEL elements or TITLE attributes.
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users. Without these, forms are very hard to use with a screen reader. Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Priority 2
Use LABEL elements for each data entry field to show what data is expected.
Make sure each INPUT field has an associated LABEL describing the field.

1050<input class='follow-by-email-address' name='email' placeholder='Email address...' type='text'/>

1051</td>

Priority 1
The 'width' attribute on the 'td' element is obsolete. Use CSS instead.
Line 1052 HTML5

1052<td width='64px'>

1053<input class='follow-by-email-submit' type='submit' value='Submit'/>

1054</td>

1055</tr>

1056</table>

1057<input name='uri' type='hidden' value='blogspot/pEcXSD'/>

1058<input name='loc' type='hidden' value='en_US'/>

1059</form>

1060</div>

1061</div>

1062<span class='item-control blog-admin'>

1063<div class='clear'></div>

1064<span class='widget-item-control'>

1065<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

1066<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=FollowByEmail&widgetId=FollowByEmail2&action=editWidget&sectionId=sidebar-right-1' onclick='return _WidgetManager._PopupConfig(document.getElementById("FollowByEmail2"));' target='configFollowByEmail2' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

1067<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

1068</a>

1069</span>

1070</span>

1071<div class='clear'></div>

1072</span>

1073</div><div class='widget HTML' data-version='1' id='HTML3'>

1074<div class='widget-content'>

1075<div style="text-align: center">

1076<div style="font-size: 14px; color: #FFFF33; background-color: #303030; padding: 6px; width: 230px; max-width: 100%;">

1077Уважаемые читатели!<br />

1078Если вы хотите получать новости блога регулярно, подпишитесь в форме, расположенной выше.<br />

1079Если вы хотите получать изредка сообщения от авторов, то пришлите нам простое письмо, нажав на картинку ниже текста.<br />

1080Dear readers!<br />

1081If you want to receive news from the blog regularly, subscribe to the form above.<br />

1082If you want to receive occasional messages from authors, please send us a simple letter by clicking on the picture below the text.<br />

Priority 2
The 'language' attribute on the 'script' element is obsolete. You can safely omit it.
Line 1083 HTML5

1083<script language="JavaScript" type="text/javascript">

1084 <!--

1085 var log = "vector_revolution";

1086 var dom = "outlook.com";

1087 var ask = "?subject=Letter%20to%20Authors%20from%20page%20";

1088 var pu = document.location.href;

1089 var sr = "https://1.bp.blogspot.com/-aX0x2htzFiE/WVs7szFNcwI/AAAAAAAAC08/Ucn4bvgenn8lN3zVn4SdxwDZbUV-nvmygCLcBGAs/s1600/mail.gif";

1090 var alt = "Согласие на рассылку новостей. Consent to the newsletter.";

1091 document.write('<a href="'+'mailto:'+log+'@'+dom+ask+pu+'"'+'title='+'"'+alt+'">');

1092 document.write('<img src="'+sr+'"'+'alt="'+alt+'"'+' />');

1093 document.write('</a>');

1094 -->

1095</script>

1096</div>

1097<br />

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

1098<a alt="google pagerank" href="http://www.mypagerank.net">

Priority 2
Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.
This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.
Priority 2
The 'border' attribute on the 'img' element is obsolete. Consider specifying 'img { border: 0; }' in CSS instead.
Line 1098 HTML5
Priority 1
An 'img' element must have an 'alt' attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Line 1098 HTML5

<img src="https://lh3.googleusercontent.com/proxy/uE3075bwaC9UyrCQMdog6w8dvzHfCr5UTanhwFb2J9jBEZiPKr_nFssGeykoXJmJ3WRiSdxWwXBrAMWHIH3iF3HdWplDZZHAK8N-DLt73Ca_gjFIF6VQpg0mNP2Bw0A5iPxnLLzobSKLLq7UUvtoS8IJTB62esRRY1KByaJW5qccX0Ztaa4d1VG23IrM1Vn6txcLDsZkJPZfNvKqxP1UXQ=s0-d" title="Googlebot last access powered by MyPagerank.Net" border="0"></a>

1099<!--LiveInternet counter--><script type="text/javascript">

1100document.write("<a href='//www.liveinternet.ru/click' "+

1101"target=_blank><img src='//counter.yadro.ru/hit?t28.20;r"+

1102escape(document.referrer)+((typeof(screen)=="undefined")?"":

1103";s"+screen.width+"*"+screen.height+"*"+(screen.colorDepth?

1104screen.colorDepth:screen.pixelDepth))+";u"+escape(document.URL)+

1105";"+Math.random()+

1106"' alt='' title='LiveInternet: показано количество просмотров и"+

1107" посетителей' "+

1108"border='0' width='88' height='120'><\/a>")

1109</script><!--/LiveInternet-->

1110<br />

Priority 1
Identify row and column headers in data tables using TH elements, and mark layout tables with role='presentation'.
Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Impact on users:

  • JAWS Reading: Treats tables without TH and ROLE as layout tables if the table contains cells above or below certain pixel sizes. This measurement is affected by browser window size, browser font size, and the browser used.
  • NVDA Reading: Applies a 'layout table' heuristic to tables without TH and ROLE which varies depending on the browser used and on the window size in some circumstances.
  • VoiceOver Safari OSX 10.9 Reading: Uses a sophisticated heuristic on tables without TH and ROLE, which is similar (but not identical) to the heuristic used by NVDA with Firefox.
Priority 1
The 'width' attribute on the 'table' element is obsolete. Use CSS instead.
Line 1111 HTML5

1111<table width="100%">

1112 <tr>

1113 <td>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href="http://pagerank.czin.eu/" title="PageRank">

Priority 2
The 'border' attribute on the 'img' element is obsolete. Consider specifying 'img { border: 0; }' in CSS instead.
Line 1113 HTML5

<img src="https://lh6.googleusercontent.com/proxy/wIfvYgwGAGRv7UWHSkTPbwm5-CeiiPxESOOFfDkKEd1BTEj-CL1qjfnvytu72qv1qAWlpRHb7IwbquPl8sdkR74cW_W4LttOEbHCJvAljg=s0-d" width="80" height="15" border="0" alt="PageRank"></a></td>

1114 <td rowspan="2">

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href="http://gpo.jmin.net/p5-df431d42a0fd39860797b0995d2a1211414a1e7aa67bf80603781bb7a4db40b7864935d1249f55c1c8767f1765dc80246715606e64947c61.html" target="_blank">

Priority 2
Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.
This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.
Priority 2
The 'border' attribute on the 'img' element is obsolete. Consider specifying 'img { border: 0; }' in CSS instead.
Line 1114 HTML5

<img src="https://lh6.googleusercontent.com/proxy/6kIIROWB96JU6wP3U0ltX6hWCdTu6HnKy7dXZZrWp1AM-hIqyMCM_gcapr2D2Q4ukSYwX53Y_MVMiQP2Pa0zdzB9c4Ci7uRzJEpUbeWiOf-wk37fTEF_3NFoQBG1gOWdldF8_LsXB03mLvnzV5f9tDEve1mY9r7O00dKQ9TW3TXoXwyyAWMA95A0IYlY-RYFH35LlFIfii6MrprwrUVdFcIQOLOkU5IIF4-XG7va3jyTV6sDOQohjF4pIwQ7FbShR3h4MSZLapAMjg=s0-d" border="0" alt="Powered by PR тИЦ SEO анализ сайта"></a><noscript>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href="http://www.mypagerank.net" alt="Google pagerank checker

Priority 1
No space between attributes.
Line 1114 HTML5
Priority 1
This page has markup errors, causing screen readers to miss content.
Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.
Priority 3
Google recommends using well-formed HTML code in your webpages. This page has mismatched tags.
Fix the critical errors listed on the Standards tab of this report. Markup errors like unclosed comments or unclosed title elements mean search engine may miss important content.
Line 1114 Google

"

Priority 1
Saw " when expecting an attribute name. Probable cause: '=' missing immediately before.
Line 1114 HTML5

">Free site service</a></noscript>

1115</td>

1116 </tr>

1117 <tr>

1118 <td> <!-- SEO Monitor by MyPagerank.Net -->

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

1119<a href="http://www.mypagerank.net/seomonitor-149929.html" target="_blank">

Priority 2
Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.
This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.
Priority 2
The 'border' attribute on the 'img' element is obsolete. Consider specifying 'img { border: 0; }' in CSS instead.
Line 1119 HTML5
Priority 1
An 'img' element must have an 'alt' attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Line 1119 HTML5

<img src="https://lh4.googleusercontent.com/proxy/uSRlI-CNkCTk9kmbND4pExFNYhx7WKZi7xMIS1khwdHxOQ30vOJ9JjezhnQDEahXrEuTwlwt77I7AFe3IbRSTAfDZpiNZ2nn_volCjWU3NkXzbnNGEg3-h_JPw=s0-d" title="seo monitor google pagerank" border="0"></a>

1120<!-- SEO Monitor by MyPagerank.Net --> &nbsp;

1121</td>

1122 </tr>

1123 </table>

1124<br />

Priority 1
Identify row and column headers in data tables using TH elements, and mark layout tables with role='presentation'.
Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Impact on users:

  • JAWS Reading: Treats tables without TH and ROLE as layout tables if the table contains cells above or below certain pixel sizes. This measurement is affected by browser window size, browser font size, and the browser used.
  • NVDA Reading: Applies a 'layout table' heuristic to tables without TH and ROLE which varies depending on the browser used and on the window size in some circumstances.
  • VoiceOver Safari OSX 10.9 Reading: Uses a sophisticated heuristic on tables without TH and ROLE, which is similar (but not identical) to the heuristic used by NVDA with Firefox.
Priority 1
The 'align' attribute on the 'table' element is obsolete. Use CSS instead.
Line 1125 HTML5
Priority 1
The 'width' attribute on the 'table' element is obsolete. Use CSS instead.
Line 1125 HTML5
Priority 1
The 'bgcolor' attribute on the 'table' element is obsolete. Use CSS instead.
Line 1125 HTML5

1125<table align="center" width="220" bgcolor="#000000"><tbody>

1126 <tr>

1127<td>

Priority 1
The 'center' element is obsolete. Use CSS instead.
Line 1127 HTML5

<center>

Priority 1
The 'font' element is obsolete. Use CSS instead.
Line 1127 HTML5

<font color="#FFFFFF">Скачай PDF-файл</font></center></td>

1128 </tr>

1129 <tr>

1130<td>

Priority 1
The 'center' element is obsolete. Use CSS instead.
Line 1130 HTML5

<center>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href="https://yadi.sk/i/7cs3FXyo3KrMcK" target="_blank" title="Пробная версия книги.">

Priority 2
Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.
This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.

<img src="https://lh5.googleusercontent.com/proxy/1yNJnQiDeSSbkYxeqhn3A_rEGS5Ov2oNzLppy2aST973dzm28oaUczhA1EEUfd4ixHPhecsTigmf92hn3dQVBixo-ijbpZqKA-ClEFqkY9ZbcrU=s0-d" width="200" alt="Векторная теория социальной революции. Пробная версия книги."></a></center></td>

1131 </tr>

1132 <tr>

1133<td>

Priority 1
The 'center' element is obsolete. Use CSS instead.
Line 1133 HTML5

<center>

Priority 1
The 'font' element is obsolete. Use CSS instead.
Line 1133 HTML5

<font color="#FFFFFF">Скачай fb2-версию для &laquo;читалки&raquo;</font></center></td>

1134 </tr>

1135 <tr>

1136<td>

Priority 1
The 'center' element is obsolete. Use CSS instead.
Line 1136 HTML5

<center>

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href="https://yadi.sk/i/AlxHUEL33KrQj7" target="_blank" title="Пробная версия книги.">

Priority 2
The 'border' attribute on the 'img' element is obsolete. Consider specifying 'img { border: 0; }' in CSS instead.
Line 1136 HTML5

<img border="0" height="195" src="https://1.bp.blogspot.com/-iH8uzDPV89k/WV_3hDdxv1I/AAAAAAAAC2g/CywRVX6BjW8QvscXq9J8mWPYwbxjiXFBgCLcBGAs/s200/Book-reader-e-ink-PDF-5.jpg" width="200" alt="Векторная теория социальной революции" /></a></center></td>

1137 </tr></tbody>

1138</table>

1139<div style="display: table; border: 1px solid #000; background: #FFF; width: 230px; max-width: 230px; padding: 3px"><noindex> <div style="display: table-cell; padding: 10px; margin: 0px; float: left; height: 70px">

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href="https://www.isnare.com/?s=author&a=Ritah+Miller" target="_new">

Priority 1
IMG elements must have an ALT attribute.
Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

Impact on users:

  • NVDA 2015.2 FF40 Windows 7 Reading: Image ignored.
  • JAWS 16.0.4350 FF40 Windows 7 Reading: Image ignored.
  • WindowEyes 8.4 IE11 Windows 7 Reading: Image ignored.
  • VoiceOver Safari OSX 10.10 Reading: Image filename read out.
  • VoiceOver Safari iOS 7.1 Touch: Image filename read out.
  • SaToGo 3.4.96.0 IE11 Windows 7 Reading: Image ignored.
Priority 2
Omitting IMG WIDTH or HEIGHT attributes means page text jumps about as images load.
This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked. Add width and height attributes to the img tag matching the image dimensions. Authoring tools like Dreamweaver can automate this process.
Priority 2
The 'border' attribute on the 'img' element is obsolete. Consider specifying 'img { border: 0; }' in CSS instead.
Line 1139 HTML5
Priority 1
An 'img' element must have an 'alt' attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Line 1139 HTML5

<img src="https://www.gravatar.com/avatar/22b27adb596b266f2f68933227bd652d?d=https%3A%2F%2Fwww.isnare.com%2Fimages%2Fui%2Favatar%2Fuser-purple.gif&amp;s=100" border="0" height="50" /></a></div> <p style="vertical-align: middle; color: #333;font-size: 14px; font-weight: bold;">

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href="https://www.isnare.com" style="color: #333; text-decoration: underline;" target="_new">Certified Inditer</a></p>

Priority 1
The 'center' element is obsolete. Use CSS instead.
Line 1139 HTML5

<center style="font-size: 12px;">Ritah Miller is a certified inditer and content contributor at<br />

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href="https://www.isnare.com" target="_new">www.isnare.com</a>.</center> </noindex></div> </div>

1140</div>

1141<div class='clear'></div>

1142<span class='widget-item-control'>

1143<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

1144<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar-right-1' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML3"));' target='configHTML3' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

1145<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

1146</a>

1147</span>

1148</span>

1149<div class='clear'></div>

1150</div>

1151<div class='widget HTML' data-version='1' id='HTML5'>

1152<script type='text/javascript'>

1153var disqus_shortname = 'vector-rev';

1154var disqus_blogger_current_url = "https://vector-rev.blogspot.com/2017/07/blog-post_16.html";

1155if (!disqus_blogger_current_url.length) {

1156disqus_blogger_current_url = "https://vector-rev.blogspot.is/2017/07/blog-post_16.html";

1157}

1158var disqus_blogger_homepage_url = "https://vector-rev.blogspot.is/";

1159var disqus_blogger_canonical_homepage_url = "https://vector-rev.blogspot.com/";

1160</script>

1161<style type='text/css'>

1162#comments {display:none;}

1163</style>

1164<script type='text/javascript'>

1165(function() {

1166 var bloggerjs = document.createElement('script');

1167 bloggerjs.type = 'text/javascript';

1168 bloggerjs.async = true;

1169 bloggerjs.src = '//' + disqus_shortname + '.disqus.com/blogger_item.js';

1170 (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(bloggerjs);

1171})();

1172</script>

1173<style type='text/css'>

1174.post-comment-link { visibility: hidden; }

1175</style>

1176<script type='text/javascript'>

1177(function() {

1178var bloggerjs = document.createElement('script');

1179bloggerjs.type = 'text/javascript';

1180bloggerjs.async = true;

1181bloggerjs.src = '//' + disqus_shortname + '.disqus.com/blogger_index.js';

1182(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(bloggerjs);

1183})();

1184</script>

1185</div></div>

1186</aside>

1187</div>

1188</div>

1189</div>

1190<div style='clear: both'></div>

1191<!-- columns -->

1192</div>

1193<!-- main -->

1194</div>

1195</div>

1196<div class='main-cap-bottom cap-bottom'>

1197<div class='cap-left'></div>

1198<div class='cap-right'></div>

1199</div>

1200</div>

1201<footer>

1202<div class='footer-outer'>

1203<div class='footer-cap-top cap-top'>

1204<div class='cap-left'></div>

1205<div class='cap-right'></div>

1206</div>

1207<div class='fauxborder-left footer-fauxborder-left'>

1208<div class='fauxborder-right footer-fauxborder-right'></div>

1209<div class='region-inner footer-inner'>

1210<div class='foot section' id='footer-1'><div class='widget HTML' data-version='1' id='HTML4'>

1211<h2 class='title'>Banners</h2>

1212<div class='widget-content'>

1213<br />

1214</div>

1215<div class='clear'></div>

1216<span class='widget-item-control'>

1217<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

1218<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=footer-1' onclick='return _WidgetManager._PopupConfig(document.getElementById("HTML4"));' target='configHTML4' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

1219<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

1220</a>

1221</span>

1222</span>

1223<div class='clear'></div>

1224</div></div>

Priority 1
Identify row and column headers in data tables using TH elements, and mark layout tables with role='presentation'.
Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Impact on users:

  • JAWS Reading: Treats tables without TH and ROLE as layout tables if the table contains cells above or below certain pixel sizes. This measurement is affected by browser window size, browser font size, and the browser used.
  • NVDA Reading: Applies a 'layout table' heuristic to tables without TH and ROLE which varies depending on the browser used and on the window size in some circumstances.
  • VoiceOver Safari OSX 10.9 Reading: Uses a sophisticated heuristic on tables without TH and ROLE, which is similar (but not identical) to the heuristic used by NVDA with Firefox.
Priority 1
The value of the 'border' attribute on the 'table' element must be either '1' or the empty string. To regulate the thickness of table borders, Use CSS instead.
Line 1225 HTML5
Priority 1
The 'cellpadding' attribute on the 'table' element is obsolete. Use CSS instead.
Line 1225 HTML5
Priority 1
The 'cellspacing' attribute on the 'table' element is obsolete. Use CSS instead.
Line 1225 HTML5

1225<table border='0' cellpadding='0' cellspacing='0' class='section-columns columns-2'>

1226<tbody>

1227<tr>

1228<td class='first columns-cell'>

1229<div class='foot section' id='footer-2-1'><div class='widget ContactForm' data-version='1' id='ContactForm1'>

1230<h2 class='title'>Форма для связи</h2>

1231<div class='contact-form-widget'>

1232<div class='form'>

1233<form name='contact-form'>

1234<p></p>

1235Имя

1236<br/>

Priority 1
This form control has no LABEL and no programmatically determined name.

A programmatically determined name allows screen readers to tell the user what the control does. To add a name do one of the following:

  • Use a LABEL element with the FOR attribute set to the ID of the form control
  • Wrap a LABEL element around the form control
  • Add a TITLE attribute
  • Add an ARIA-LABELLEDBY attribute (not supported in all screen readers)
  • Add an ARIA-LABEL attribute (not supported in all screen readers)
Priority 1
This form has fields without LABEL elements or TITLE attributes.
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users. Without these, forms are very hard to use with a screen reader. Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Priority 2
Use LABEL elements for each data entry field to show what data is expected.
Make sure each INPUT field has an associated LABEL describing the field.

1237<input class='contact-form-name' id='ContactForm1_contact-form-name' name='name' size='30' type='text' value=''/>

1238<p></p>

1239Электронная почта

1240<span style='font-weight: bolder;'>*</span>

1241<br/>

Priority 1
This form control has no LABEL and no programmatically determined name.

A programmatically determined name allows screen readers to tell the user what the control does. To add a name do one of the following:

  • Use a LABEL element with the FOR attribute set to the ID of the form control
  • Wrap a LABEL element around the form control
  • Add a TITLE attribute
  • Add an ARIA-LABELLEDBY attribute (not supported in all screen readers)
  • Add an ARIA-LABEL attribute (not supported in all screen readers)
Priority 1
This form has fields without LABEL elements or TITLE attributes.
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users. Without these, forms are very hard to use with a screen reader. Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Priority 2
Use LABEL elements for each data entry field to show what data is expected.
Make sure each INPUT field has an associated LABEL describing the field.

1242<input class='contact-form-email' id='ContactForm1_contact-form-email' name='email' size='30' type='text' value=''/>

1243<p></p>

1244Сообщение

1245<span style='font-weight: bolder;'>*</span>

1246<br/>

Priority 1
This form control has no LABEL and no programmatically determined name.

A programmatically determined name allows screen readers to tell the user what the control does. To add a name do one of the following:

  • Use a LABEL element with the FOR attribute set to the ID of the form control
  • Wrap a LABEL element around the form control
  • Add a TITLE attribute
  • Add an ARIA-LABELLEDBY attribute (not supported in all screen readers)
  • Add an ARIA-LABEL attribute (not supported in all screen readers)
Priority 1
This form has fields without LABEL elements or TITLE attributes.
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users. Without these, forms are very hard to use with a screen reader. Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Priority 2
Use LABEL elements for each data entry field to show what data is expected.
Make sure each INPUT field has an associated LABEL describing the field.

1247<textarea class='contact-form-email-message' cols='25' id='ContactForm1_contact-form-email-message' name='email-message' rows='5'></textarea>

1248<p></p>

1249<input class='contact-form-button contact-form-button-submit' id='ContactForm1_contact-form-submit' type='button' value='Отправить'/>

1250<p></p>

1251<div style='text-align: center; max-width: 222px; width: 100%'>

1252<p class='contact-form-error-message' id='ContactForm1_contact-form-error-message'></p>

1253<p class='contact-form-success-message' id='ContactForm1_contact-form-success-message'></p>

1254</div>

1255</form>

1256</div>

1257</div>

1258<div class='clear'></div>

1259<span class='widget-item-control'>

1260<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

1261<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=ContactForm&widgetId=ContactForm1&action=editWidget&sectionId=footer-2-1' onclick='return _WidgetManager._PopupConfig(document.getElementById("ContactForm1"));' target='configContactForm1' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

1262<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

1263</a>

1264</span>

1265</span>

1266<div class='clear'></div>

1267</div></div>

1268</td>

1269<td class='columns-cell'>

1270<div class='foot no-items section' id='footer-2-2'></div>

1271</td>

1272</tr>

1273</tbody>

1274</table>

1275<!-- outside of the include in order to lock Attribution widget -->

Priority 1
Attribute ':name' not allowed on element.
Line 1276 HTML5

1276<div class='foot section' id='footer-3' name='Нижний колонтитул'><div class='widget Attribution' data-version='1' id='Attribution1'>

1277<div class='widget-content' style='text-align: center;'>

1278Автор изображений для темы:

Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

<a href='http://www.istockphoto.com/file_closeup.php?id=4489297&platform=blogger' target='_blank'>imagedepotpro</a>. Технологии <a href='https://www.blogger.com' target='_blank'>Blogger</a>.

1279</div>

1280<div class='clear'></div>

1281<span class='widget-item-control'>

1282<span class='item-control blog-admin'>

Priority 1
Each A element must contain text or an IMG with an ALT attribute.
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
Priority 1
Provide a way to skip repetitive navigation links.
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>

1283<a class='quickedit' href='//www.blogger.com/rearrange?blogID=8956464986740803789&widgetType=Attribution&widgetId=Attribution1&action=editWidget&sectionId=footer-3' onclick='return _WidgetManager._PopupConfig(document.getElementById("Attribution1"));' target='configAttribution1' title='Изменить'>

Priority 2
Use text links rather than image links. In general, text links are more easily recognized as clickable.
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image. Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping'). Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options.

1284<img alt='' height='18' src='https://resources.blogblog.com/img/icon18_wrench_allbkg.png' width='18'/>

1285</a>

1286</span>

1287</span>

1288<div class='clear'></div>

1289</div></div>

1290</div>

1291</div>

1292<div class='footer-cap-bottom cap-bottom'>

1293<div class='cap-left'></div>

1294<div class='cap-right'></div>

1295</div>

1296</div>

1297</footer>

1298<!-- content -->

1299</div>

1300</div>

1301<div class='content-cap-bottom cap-bottom'>

1302<div class='cap-left'></div>

1303<div class='cap-right'></div>

1304</div>

1305</div>

1306</div>

1307<script type='text/javascript'>

1308 window.setTimeout(function() {

1309 document.body.className = document.body.className.replace('loading', '');

1310 }, 10);

1311 </script>

1312<script src='https://apis.google.com/js/plusone.js' type='text/javascript'></script>

1313

1314<script type="text/javascript" src="https://www.blogger.com/static/v1/widgets/2859494812-widgets.js"></script>

1315<script type='text/javascript'>

1316window['__wavt'] = 'AOuZoY5y39OMB2ZWPb_YErteFQZhlR2grw:1499852889541';_WidgetManager._Init('//www.blogger.com/rearrange?blogID\x3d8956464986740803789','//vector-rev.blogspot.is/2017/07/blog-post_16.html','8956464986740803789');

1317_WidgetManager._SetDataContext([{'name': 'blog', 'data': {'blogId': '8956464986740803789', 'title': 'Векторная теория социальной революции', 'url': 'https://vector-rev.blogspot.is/2017/07/blog-post_16.html', 'canonicalUrl': 'https://vector-rev.blogspot.com/2017/07/blog-post_16.html', 'homepageUrl': 'https://vector-rev.blogspot.is/', 'searchUrl': 'https://vector-rev.blogspot.is/search', 'canonicalHomepageUrl': 'https://vector-rev.blogspot.com/', 'blogspotFaviconUrl': 'https://vector-rev.blogspot.is/favicon.ico', 'bloggerUrl': 'https://www.blogger.com', 'hasCustomDomain': false, 'httpsEnabled': true, 'enabledCommentProfileImages': true, 'gPlusViewType': 'FILTERED_POSTMOD', 'adultContent': false, 'analyticsAccountNumber': '', 'encoding': 'UTF-8', 'locale': 'ru', 'localeUnderscoreDelimited': 'ru', 'languageDirection': 'ltr', 'isPrivate': false, 'isMobile': false, 'isMobileRequest': false, 'mobileClass': '', 'isPrivateBlog': false, 'feedLinks': '\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Векторная теория социальной революции - Atom\x22 href\x3d\x22https://vector-rev.blogspot.com/feeds/posts/default\x22 /\x3e\n\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/rss+xml\x22 title\x3d\x22Векторная теория социальной революции - RSS\x22 href\x3d\x22https://vector-rev.blogspot.com/feeds/posts/default?alt\x3drss\x22 /\x3e\n\x3clink rel\x3d\x22service.post\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Векторная теория социальной революции - Atom\x22 href\x3d\x22https://www.blogger.com/feeds/8956464986740803789/posts/default\x22 /\x3e\n\n\x3clink rel\x3d\x22alternate\x22 type\x3d\x22application/atom+xml\x22 title\x3d\x22Векторная теория социальной революции - Atom\x22 href\x3d\x22https://vector-rev.blogspot.com/feeds/4865024095207574136/comments/default\x22 /\x3e\n', 'meTag': '', 'openIdOpTag': '', 'adsenseHostId': 'ca-host-pub-1556223355139109', 'adsenseHasAds': true, 'ieCssRetrofitLinks': '\x3c!--[if IE]\x3e\x3cscript type\x3d\x22text/javascript\x22 src\x3d\x22https://www.blogger.com/static/v1/jsbin/3409755933-ieretrofit.js\x22\x3e\x3c/script\x3e\n\x3c![endif]--\x3e', 'view': '', 'dynamicViewsCommentsSrc': '//www.blogblog.com/dynamicviews/4224c15c4e7c9321/js/comments.js', 'dynamicViewsScriptSrc': '//www.blogblog.com/dynamicviews/f044faeb4ea5d71b', 'plusOneApiSrc': 'https://apis.google.com/js/plusone.js', 'sharing': {'platforms': [{'name': 'Получить ссылку', 'key': 'link', 'shareMessage': 'Получить ссылку', 'target': ''}, {'name': 'Facebook', 'key': 'facebook', 'shareMessage': 'Поделиться в Facebook', 'target': 'facebook'}, {'name': 'Написать об этом в блоге', 'key': 'blogThis', 'shareMessage': 'Написать об этом в блоге', 'target': 'blog'}, {'name': 'Twitter', 'key': 'twitter', 'shareMessage': 'Поделиться в Twitter', 'target': 'twitter'}, {'name': 'Pinterest', 'key': 'pinterest', 'shareMessage': 'Поделиться в Pinterest', 'target': 'pinterest'}, {'name': 'Google+', 'key': 'googlePlus', 'shareMessage': 'Поделиться в Google+', 'target': 'googleplus'}, {'name': 'Электронная почта', 'key': 'email', 'shareMessage': 'Электронная почта', 'target': 'email'}], 'googlePlusShareButtonWidth': 300, 'googlePlusBootstrap': '\x3cscript type\x3d\x22text/javascript\x22\x3ewindow.___gcfg \x3d {\x27lang\x27: \x27ru\x27};\x3c/script\x3e'}, 'hasCustomJumpLinkMessage': false, 'jumpLinkMessage': 'Далее...', 'pageType': 'item', 'postId': '4865024095207574136', 'postImageThumbnailUrl': 'https://img.youtube.com/vi/kAUS8pav1sw/default.jpg', 'postImageUrl': 'https://img.youtube.com/vi/kAUS8pav1sw/hqdefault.jpg', 'pageName': 'Читатели книги \x22Векторная теория социальной революции\x22', 'pageTitle': 'Векторная теория социальной революции: Читатели книги \x22Векторная теория социальной революции\x22', 'metaDescription': ''}}, {'name': 'features', 'data': {'unsupported_browser_message': 'false', 'lightbox_img_parsing': 'false', 'sharing_get_link_dialog': 'false'}}, {'name': 'messages', 'data': {'edit': 'Изменить', 'linkCopiedToClipboard': 'Ссылка скопирована в буфер обмена!', 'ok': 'ОК', 'postLink': 'Ссылка на сообщение'}}, {'name': 'template', 'data': {'name': 'custom', 'localizedName': 'Дополнительно', 'isResponsive': false, 'isAlternateRendering': false, 'isCustom': true}}, {'name': 'view', 'data': {'classic': {'name': 'classic', 'url': '?view\x3dclassic'}, 'flipcard': {'name': 'flipcard', 'url': '?view\x3dflipcard'}, 'magazine': {'name': 'magazine', 'url': '?view\x3dmagazine'}, 'mosaic': {'name': 'mosaic', 'url': '?view\x3dmosaic'}, 'sidebar': {'name': 'sidebar', 'url': '?view\x3dsidebar'}, 'snapshot': {'name': 'snapshot', 'url': '?view\x3dsnapshot'}, 'timeslide': {'name': 'timeslide', 'url': '?view\x3dtimeslide'}, 'isMobile': false, 'title': 'Читатели книги \x22Векторная теория социальной революции\x22', 'description': 'Векторная теория социальной революции', 'featuredImage': 'https://lh6.googleusercontent.com/proxy/-5LzHID3JZ8E6ktfRig5OT6zC01W3beLn5mdQiRnfHryxxooxKOPa9GP-TZYhwO2TTTMSlx9Kr7Rbvx9ryTdCNQmcsNpYsld', 'url': 'https://vector-rev.blogspot.is/2017/07/blog-post_16.html', 'type': 'item', 'isSingleItem': true, 'isMultipleItems': false, 'isError': false, 'isPage': false, 'isPost': true, 'isHomepage': false, 'isArchive': false, 'isLabelSearch': false, 'postId': 4865024095207574136}}]);

1318_WidgetManager._RegisterWidget('_NavbarView', new _WidgetInfo('Navbar1', 'navbar', null, document.getElementById('Navbar1'), {}, 'displayModeFull'));

1319_WidgetManager._RegisterWidget('_HeaderView', new _WidgetInfo('Header1', 'header', null, document.getElementById('Header1'), {}, 'displayModeFull'));

1320_WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML2', 'crosscol', null, document.getElementById('HTML2'), {}, 'displayModeFull'));

1321_WidgetManager._RegisterWidget('_BlogView', new _WidgetInfo('Blog1', 'main', null, document.getElementById('Blog1'), {'cmtInteractionsEnabled': false, 'showBacklinks': true, 'postId': '4865024095207574136', 'lightboxEnabled': true, 'lightboxModuleUrl': 'https://www.blogger.com/static/v1/jsbin/2425708351-lbx__ru.js', 'lightboxCssUrl': 'https://www.blogger.com/static/v1/v-css/368954415-lightbox_bundle.css'}, 'displayModeFull'));

1322_WidgetManager._RegisterWidget('_PopularPostsView', new _WidgetInfo('PopularPosts1', 'main', null, document.getElementById('PopularPosts1'), {}, 'displayModeFull'));

1323_WidgetManager._RegisterWidget('_BlogSearchView', new _WidgetInfo('BlogSearch1', 'sidebar-right-1', null, document.getElementById('BlogSearch1'), {}, 'displayModeFull'));

1324_WidgetManager._RegisterWidget('_ProfileView', new _WidgetInfo('Profile1', 'sidebar-right-1', null, document.getElementById('Profile1'), {}, 'displayModeFull'));

1325_WidgetManager._RegisterWidget('_BlogArchiveView', new _WidgetInfo('BlogArchive1', 'sidebar-right-1', null, document.getElementById('BlogArchive1'), {'languageDirection': 'ltr', 'loadingMessage': 'Загрузка\x26hellip;'}, 'displayModeFull'));

1326_WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML1', 'sidebar-right-1', null, document.getElementById('HTML1'), {}, 'displayModeFull'));

1327_WidgetManager._RegisterWidget('_FollowByEmailView', new _WidgetInfo('FollowByEmail2', 'sidebar-right-1', null, document.getElementById('FollowByEmail2'), {}, 'displayModeFull'));

1328_WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML3', 'sidebar-right-1', null, document.getElementById('HTML3'), {}, 'displayModeFull'));

1329_WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML5', 'sidebar-right-1', null, document.getElementById('HTML5'), {}, 'displayModeFull'));

1330_WidgetManager._RegisterWidget('_HTMLView', new _WidgetInfo('HTML4', 'footer-1', null, document.getElementById('HTML4'), {}, 'displayModeFull'));

1331_WidgetManager._RegisterWidget('_ContactFormView', new _WidgetInfo('ContactForm1', 'footer-2-1', null, document.getElementById('ContactForm1'), {'contactFormMessageSendingMsg': 'Отправка...', 'contactFormMessageSentMsg': 'Сообщение отправлено.', 'contactFormMessageNotSentMsg': 'Сообщение не отправлено. Повторите попытку позже.', 'contactFormInvalidEmailMsg': 'Требуется действительный адрес электронной почты.', 'contactFormEmptyMessageMsg': 'Поле текста сообщения не может быть пустым.', 'title': 'Форма для связи', 'blogId': '8956464986740803789', 'contactFormNameMsg': 'Имя', 'contactFormEmailMsg': 'Электронная почта', 'contactFormMessageMsg': 'Сообщение', 'contactFormSendMsg': 'Отправить', 'submitUrl': 'https://www.blogger.com/contact-form.do'}, 'displayModeFull'));

1332_WidgetManager._RegisterWidget('_AttributionView', new _WidgetInfo('Attribution1', 'footer-3', null, document.getElementById('Attribution1'), {}, 'displayModeFull'));

1333</script>

1334</body>

1335</html>