Page Title: Rad Geek People's Daily – Accessibility statement

  • This webpage makes use of the TITLE meta tag - this is good for search engine optimization.

Page Description:

  • This webpage DOES NOT make use of the DESCRIPTION meta tag - this is NOT GOOD for search engine optimization.

Page Keywords:

  • This webpage DOES NOT make use of the KEYWORDS meta tag - whilst search engines nowadays do not put too much emphasis on this meta tag including them in your website does no harm.

Page Text: Rad Geek People's Daily official state media for a secessionist republic of one This site is designed to be accessible by any web device. It looks best in those that support web standards . This is a page from the Rad Geek People’s Daily weblog, which has been written and maintained at radgeek.com since 2004. Accessibility statement. (posted 21 January 2004 , 4pm / revised 7pm 5 July 2008) This is the official accessibility statement for Rad Geek People’s Daily . If you have any questions, comments, or concerns, please feel free to contact me about them. Access keys Many web browsers support quick navigation using keys defined on the website. In Firefox versions 2 and later, you can press ALT + Shift + an access key. In most other Windows browsers, you can press ALT + an access key; on Macintosh you can press Control + an access key. All the pages on this site define the following access keys: Access key 1: Front page Access key 3: Site Map Access key 4: Search Access key 9: Contact me Access key 0: Accessibility statement Although there are no agreed standards for which keys should be assigned to which features, all of these access key assignments do follow common conventions, and so are likely to be similar to the assignments on other websites designed for accessibility. Standards compliance All pages on this website are Bobby AAA Approved , complying with all the Bobby guidelines . I should warn you that this is a judgment call: many accessibility features can be quantified and tested, but many others cannot. I have reviewed all the guidelines and believe that all these pages are in compliance. All pages on this website are WCAG AAA approved, complying with all priority 1, 2, and 3 guidelines of the W3C Web Content Accessibility Guidelines 1.0 . This is also a judgment call: many guidelines cannot be tested automatically, and indeed some are intentionally vague. I have reviewed the guidelines and believe that all these pages are in full compliance. All pages on this site are Section 508 approved, complying with all of the U.S. Federal Government Section 508 Guidelines. Once again, a judgment call; I have reviewed the guidelines, and believe that all these pages comply. All pages on this website conform to open web standards for XHTML 1.1 and CSS 3 . This is not a judgment call: automated programs can determine with 100% accuracy whether or not a page validates according to the XHTML and CSS standards. All pages are checked with the W3C ‘s (X)HTML validator and CSS validator ). All pages on this website use structured semantic markup. h1 tags are used for page titles, h2 tags for post titles, h3 tags for subtitles and section titles. For example, on this page, JAWS users can skip to the next section within the accessibility statement by pressing ALT+INSERT+3 . Navigation aids All pages have links for home, up, and (where applicable) previous and next defined to aid navigation in text-only browsers. All pages include a search box, and a link to a stand-alone search page (access key 4). Visual design This site uses Cascading Style Sheets for visual layout (but is designed to be readable even if your web browser or web browsing device does not support stylesheets at all). The color schemes used on this site have been checked (using Vischeck ) for accessibility to the color-blind. This site uses only relative font sizes, compatible with the user-specified text-size option in visual browsers. Links Most links have a title attribute which describes the link in greater detail, unless the text of the link already fully describes the target (such as the headline of an article). Links are written to make sense out of context. Images All content images used on this website include ALT attributes that substitute for the content of the image as accurately as possible. Purely decorative graphics include empty ALT attributes (to avoid cluttering up the reading or the layout of the page in alternative browsers). Complex images include LONGDESC attributes or inline descriptions to explain the significance of each image to non-visual readers. —Rad Geek Anticopyright. This was written 2004–2008 by Rad Geek . Feel free to reprint if you like it. This machine kills intellectual monopolists.

  • This webpage has 671 words which is between the recommended minimum of 250 words and the recommended maximum of 2500 words - GOOD WORK.

Header tags:

  • It appears that you are using header tags - this is a GOOD thing!

Spelling errors:

  • This webpage has 1 words which may be misspelt.

Possibly mis-spelt word: weblog

Suggestion: we blog
Suggestion: we-blog
Suggestion: web log
Suggestion: web-log
Suggestion: blogged

Broken links:

  • This webpage has no broken links that we can detect - GOOD WORK.

Broken image links:

  • This webpage has no broken image links that we can detect - GOOD WORK.

CSS over tables for layout?:

  • It appears that this page uses DIVs for layout this is a GOOD thing!

Last modified date:

  • It appears that this page was updated on the Saturday, April 2, 2022 which is within the last thirty days - this is a GOOD thing!

Images that are being re-sized:

  • This webpage has no images that are being re-sized by the browser - GOOD WORK.

Images that are being re-sized:

  • This webpage has 1 images that do not have their width and height specified.

Mobile friendly:

  • After testing this webpage it appears NOT to be mobile friendly - this is NOT a good thing!

Links with no anchor text:

  • This webpage has 1 links that do not contain anchor text - this is NOT a good thing.

Image link URL:

W3C Validation:

Print friendly?:

  • It appears that the webpage does NOT use CSS stylesheets to provide print functionality - this is a BAD thing.

GZIP Compression enabled?:

  • It appears that the serrver does NOT have GZIP Compression enabled - this is a NOT a good thing!