Web Content Accessibility Guidelines

The Web Content Accessibility Guidelines (WCAG) are part of a series of web accessibility guidelines published by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C), the main international standards organization for the Internet. They are a set of recommendations for making Web content more accessible, primarily for people with disabilities—but also for all user agents, including highly limited devices, such as mobile phones. WCAG 2.0, was published in December 2008 and became an ISO standard, ISO/IEC 40500:2012 in October 2012. WCAG 2.1 became a W3C Recommendation in June 2018.

Earlier guidelines

The first web accessibility guideline was compiled by Gregg Vanderheiden and released in January 1995, just after the 1994 Second International Conference on the World-Wide Web (WWW II) in Chicago (where Tim Berners-Lee first mentioned disability access in a keynote speech after seeing a pre-conference workshop on accessibility led by Mike Paciello).[1]

Over 38 different Web access guidelines followed from various authors and organizations over the next few years.[2] These were brought together in the Unified Web Site Accessibility Guidelines compiled at the University of Wisconsin–Madison.[3] Version 8 of the Unified Web Site Accessibility Guidelines, published in 1998, served as the starting point for the W3C's WCAG 1.0.[4]

WCAG 1.0

The WCAG 1.0 was published and became a W3C recommendation on 5 May 1999. They have since been superseded by WCAG 2.0.

WCAG 1.0 consist of 14 guidelines—each of which describes a general principle of accessible design. Each guideline covers a basic theme of web accessibility and is associated with one or more checkpoints that describes how to apply that guideline to particular webpage features.

  • Guideline 1: Provide equivalent alternatives to auditory and visual content
  • Guideline 2: Don’t rely on colour alone
  • Guideline 3: Use markup and style sheets, and do so properly
  • Guideline 4: Clarify natural language usage
  • Guideline 5: Create tables that transform gracefully
  • Guideline 6: Ensure that pages featuring new technologies transform gracefully
  • Guideline 7: Ensure user control of time sensitive content changes
  • Guideline 8: Ensure direct accessibility of embedded user interfaces
  • Guideline 9: Design for device independence
  • Guideline 10: User interim solutions
  • Guideline 11: Use W3C technologies and guidelines
  • Guideline 12: Provide context and orientation information
  • Guideline 13: Provide clear navigation mechanisms
  • Guideline 14: Ensure that documents are clear and simple

Each of the in total 65 WCAG 1.0 checkpoints has an assigned priority level based on the checkpoint's impact on accessibility:

  • Priority 1: Web developers must satisfy these requirements, otherwise it will be impossible for one or more groups to access the Web content. Conformance to this level is described as A.
  • Priority 2: Web developers should satisfy these requirements, otherwise some groups will find it difficult to access the Web content. Conformance to this level is described as AA or Double-A.
  • Priority 3: Web developers may satisfy these requirements to make it easier for some groups to access the Web content. Conformance to this level is described as AAA or Triple-A.

WCAG Samurai

In February 2008, The WCAG Samurai, a group of developers independent of the W3C, and led by Joe Clark, published corrections for, and extensions to, the WCAG 1.0.[5]

WCAG 2.0

WCAG 2.0 was published as a W3C Recommendation on 11 December 2008.[6][7] It consists of twelve guidelines (untestable) organized under four principles (websites must be perceivable, operable, understandable, and robust). Each guideline has testable success criteria (61 in all).[8] The W3C's Techniques for WCAG 2.0[9] is a list of techniques that help authors meet the guidelines and success criteria. The techniques are periodically updated whereas the principles, guidelines and success criteria are stable and do not change.[10]



Information and user interface components must be presentable to users in ways they can perceive.

  • Guideline 1.1: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
  • Guideline 1.2: Time-based media: Provide alternatives for time-based media.
  • Guideline 1.3: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
  • Guideline 1.4: Make it easier for users to see and hear content including separating foreground from background.


User interface components and navigation must be operable.

  • Guideline 2.1: Make all functionality available from a keyboard.
  • Guideline 2.2: Provide users enough time to read and use content.
  • Guideline 2.3: Do not design content in a way that is known to cause seizures.
  • Guideline 2.4: Provide ways to help users navigate, find content, and determine where they are.


Information and the operation of user interface must be understandable.

  • Guideline 3.1: Make text content readable and understandable.
  • Guideline 3.2: Make web pages appear and operate in predictable ways.
  • Guideline 3.3: Help users avoid and correct mistakes.


Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

  • Guideline 4.1.: Maximize compatibility with current and future user agents, including assistive technologies.

WCAG 2.0 uses the same three levels of conformance (A, AA, AAA) as WCAG 1.0, but has redefined them. The WCAG working group maintains an extensive list of web accessibility techniques and common failure cases for WCAG 2.0.[11]

Document history

The first concept proposal of WCAG 2.0 was published on 25 January 2001. In the following years new versions were published intended to solicit feedback from accessibility experts and members of the disability community. On 27 April 2006 a "Last Call Working Draft" was published.[12] Due to the many amendments that were necessary, WCAG 2.0 was published again as a concept proposal on 17 May 2007, followed by a second "Last Call Working Draft" on 11 December 2007.[13][14] In April 2008 the guidelines became a "Candidate Recommendation".[15] On 3 November 2008 the guidelines became a "Proposed Recommendation". WCAG 2.0 was published as a W3C Recommendation on 11 December 2008.

A comparison of WCAG 1.0 checkpoints and WCAG 2.0 success criteria is available.[16]

In October 2012, WCAG 2.0 was accepted by the International Organization for Standardization as an ISO International Standard, ISO/IEC 40500:2012.[17][18][19]

In early 2014, WCAG 2.0's Level A and Level AA success criteria were incorporated as references in clause 9.2 ("Web content requirements") of the European standard EN 301 549 published by ETSI.[20] EN 301 549 was produced in response to a mandate that the European Commission gave to the three official European standardisation bodies (CEN, CENELEC and ETSI) and is the first European standard for ICT products and services.[21][22]

WCAG 2.1

WCAG 2.1 became a W3C Recommendation on 5 June 2018.[23] According to the W3C, it was:[23]

...initiated with the goal to improve accessibility guidance for three major groups: users with cognitive or learning disabilities, users with low vision, and users with disabilities on mobile devices

and is backwards-compatible with WCAG 2.0, which it extends with a further 17 success criteria.[23]

Legal obligations

Businesses that have an online presence should provide accessibility to disabled users. Not only are there ethical and commercial justifications[24] for implementing the Web Content Accessibility Guidelines, in some countries and jurisdictions, there are also legal reasons. Under UK law, if a business's website is not accessible, then the website owner could be sued for discrimination.[25]

United States

In January 2017, the U.S. Access Board approved a final rule to update Section 508 of the Rehabilitation Act of 1973. The new rule adopts seventeen WCAG 2.0 success criteria, but 22 of the 38 existing A-level and AA-level criteria were already covered by existing Section 508 guidelines. The rule requires adherence to the new standards twelve months from its date of publication in the federal register. [26] [27]

In 2017, a Federal Court in Florida identified the WCAG guidelines as the "industry standard" for website accessibility and found that Winn Dixie Store, Inc., violated the Americans with Disabilities Act by failing to render its website accessible to the sight impaired.[28]

European Union

In October 2016, the European Parliament approved the directive 2016/2102 that requires websites and mobile applications of public sector bodies to conform with WCAG 2.0 Level AA.[29] New websites must comply from 23 September 2019 on, old websites from 23 September 2020 on and mobile applications from 23 June 2021 on.[30]

United Kingdom

In January 2012, the Royal National Institute for the Blind (RNIB) in the United Kingdom issued a press release stating that it had served legal proceedings against low-cost airline Bmibaby[31] over their "failure to ensure web access for blind and partially sighted customers". As of October 2011, at least two actions against websites had been initiated by the RNIB, and settled without the cases being heard by a court.[25]

An employment tribunal finding against the Project Management Institute (PMI), was decided in October 2006, and the company was ordered to pay compensation of £3,000 for discrimination.[32]


The 2010/2012 Jodhan decision[33] caused the Canadian federal government to require all online web pages, documents and videos available externally and internally to meet the accessibility requirements of WCAG 2.0.[34]


The Australian government has also mandated via the Disability Discrimination Act 1992 that all Australian government websites meet the WCAG accessibility requirements.[35]


The Israeli Ministry of Justice published regulations in early 2014, requiring Internet websites to comply with Israeli Standard 5568, which is based on the W3C Web Content Accessibility Guidelines 2.0.

The main differences between the Israeli standard and the W3C standard concern the requirements to provide captions and texts for audio and video media. The Israeli standards are somewhat more lenient, reflecting the current technical difficulties in providing such captions and texts in Hebrew.[36]


  1. ^ Vanderheiden, Gregg C. (31 January 1995). "Design of HTML (Mosaic) Pages to Increase their Accessibility to Users with Disabilities; Strategies for Today and Tomorrow". Trace Center, University of Wisconsin–Madison. Retrieved 2012-09-22.
  2. ^ "References: Designing Accessible HTML Pages -- guidelines and overview documents". World Wide Web Consortium. Retrieved 2012-09-22.
  3. ^ "Trace Center". Trace Center, University of Wisconsin–Madison. Retrieved 2012-09-22.
  4. ^ Vanderheiden, Gregg C.; Chisholm, Wendy A., eds. (20 January 1998). "Unified Web Site Accessibility Guidelines". Trace Center, University of Wisconsin–Madison. Retrieved 2012-09-22.
  5. ^ "Home Page". WCAG Samurai. Archived from the original on 2013-01-13.
  6. ^ "Web Content Accessibility Guidelines (WCAG) 2.0 – W3C Recommendation 11 December 2008". W3.org. Retrieved 27 July 2013.
  7. ^ W3C: W3C Web Standard Defines Accessibility for Next Generation Web (press release, 11 December 2008).
  8. ^ "Web Content Accessibility Guidelines (WCAG) 2.0". W3C. Retrieved 2014-12-17.
  9. ^ "Techniques for WCAG 2.0". W3C. Retrieved 2014-12-17.
  10. ^ "Understanding Techniques for WCAG Success Criteria". W3C. Retrieved 2014-12-17.
  11. ^ "Techniques for WCAG 2.0". W3.org. Retrieved 27 July 2013.
  12. ^ "Web Content Accessibility Guidelines 2.0 – W3C Working Draft 27 April 2006". W3C.
  13. ^ "Web Content Accessibility Guidelines 2.0 – W3C Working Draft 17 May 2007". W3C.
  14. ^ "Web Content Accessibility Guidelines 2.0 – W3C Working Draft 11 December 2007". W3C.
  15. ^ "WCAG 2.0 Candidate Recommendation Implementation Information". W3C.
  16. ^ "Comparison of WCAG 1.0 Checkpoints to WCAG 2.0, in Numerical Order". W3.org. Retrieved 27 July 2013.
  17. ^ Henry, Shawn (2012-10-15). "WCAG 2.0 is now also ISO/IEC 40500!". World Wide Web Consortium. Retrieved 23 October 2012.
  18. ^ "W3C Web Content Accessibility Guidelines 2.0 approved as an ISO/IEC International Standard". World Wide Web Consortium. 2012-10-15. Retrieved 23 October 2012.
  19. ^ "ISO/IEC 40500:2012 - Information technology -- W3C Web Content Accessibility Guidelines (WCAG) 2.0". ISO. Retrieved 23 October 2012.
  20. ^ ETSI: EN 301 549 V1.1.1 (2014-02): Accessibility requirements suitable for public procurement of ICT products and services in Europe. Accessed 27 November 2015.
  21. ^ CEN-CENELEC: New European Standard will help to make ICT products and services accessible for all. 19 February 2014. Accessed 27 November 2015.
  22. ^ CEN-CENELEC: Mandate 376. (No date). Accessed 27 November 2015.
  23. ^ a b c "Web Content Accessibility Guidelines (WCAG) 2.1". WC3. Retrieved 13 March 2019.
  24. ^ "Commercial Justifications for WCAG 2.0". Isamuel.com. 2012-04-12. Archived from the original on 5 April 2016. Retrieved 27 July 2013.CS1 maint: BOT: original-url status unknown (link)
  25. ^ a b "Disabled access to websites under UK law". Out-Law.com. October 2011. Retrieved 15 January 2015.
  26. ^ "Information and Communication Technology (ICT) Final Standards and Guidelines" (PDF). United States Access Board. 9 Jan 2017. Retrieved 10 Jan 2017.
  27. ^ "Final Regulatory Impact Analysis: Final Rule to Update the Section 508 Standards and Section 255 Guidelines". United States Access Board. 5 Jan 2017. Retrieved 10 Jan 2017.
  28. ^ https://scholar.google.com/scholar_case?case=6744502269111605689&q=257+F.Supp.3d+1340&hl=en&as_sdt=20006
  29. ^ "COMMUNICATION FROM THE COMMISSION TO THE EUROPEAN PARLIAMENT pursuant to Article 294(6) of the Treaty on the Functioning of the European Union concerning the position of the Council on the adoption of a Proposal for a Directive of the European Parliament and of the Council on the accessibility of the websites and mobile applications of public sector bodies". Publications Office of the European Union. 2016-07-18. Retrieved 2017-02-10.
  30. ^ "DIRECTIVE (EU) 2016/2102 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies, Article 12". Publications Office of the European Union. 2016-10-26. Retrieved 2017-02-10.
  31. ^ "serves legal proceedings on bmibaby". RNIB. 2012-01-27. Retrieved 27 July 2013.
  32. ^ "Computer-based exam discriminated against blind candidate". Out-law.com. Retrieved 27 July 2013.
  33. ^ "Jodhan decision". Ccdonline.ca. 2012-05-30. Retrieved 27 July 2013.
  34. ^ "Canadian Treasury Board Secretariat Standard on Web Accessibility". Tbs-sct.gc.ca. 2011-08-01. Retrieved 27 July 2013.
  35. ^ "Accessibility". Web Guide. Retrieved 27 July 2013.
  36. ^ "Israel Technology Law Blog, Website Accessibility Requirements".

External links



AnySurfer is a Belgian organisation that promotes the accessibility of websites, apps, and digital documents for disabled individuals. It is also the name of a quality label which websites can obtain if they are fully accessible. AnySurfer is a national project run by Blindenzorg Licht en Liefde, a Belgian non-profit organisation that provides aid to the blind and the visually impaired.The checklist AnySurfer uses when allocating the AnySurfer label is based on the Web Content Accessibility Guidelines (WCAG 2.0).

Blink element

The blink element is a non-standard HTML element that indicates to a user agent (generally a web browser) that the page author intends the content of the element to blink (that is, alternate between being visible and invisible). The element was introduced in Netscape Navigator but is no longer supported and often ignored by modern Web browsers; some, such as Internet Explorer, never supported the element at all.Despite its initial popularity among home users in the 1990s, it has since fallen out of favor due to its overuse and the difficulty it presents in reading. Lou Montulli, often credited as the inventor of the blink element, has said that he considers "the blink tag to be the worst thing I've ever done for the Internet", although he claims he only suggested the idea, without writing any actual code.

... At some point in the evening I mentioned that it was sad that Lynx was not going to be able to display many of the HTML extensions that we were proposing, I also pointed out that the only text style that Lynx could exploit given its environment was blinking text. We had a pretty good laugh at the thought of blinking text, and talked about blinking this and that and how absurd the whole thing would be. ... Saturday morning rolled around and I headed into the office only to find what else but, blinking text. It was on the screen blinking in all its glory, and in the browser. How could this be, you might ask? It turns out that one of the engineers liked my idea so much that he left the bar sometime past midnight, returned to the office and implemented the blink tag overnight. He was still there in the morning and quite proud of it.

Deque Systems

Deque Systems ( DEE-kew) is a digital accessibility company based in Herndon, Virginia with additional offices in Ann Arbor, Michigan and Secunderabad, India. The company was started in 1999 and produces accessibility software in addition to offering accessibility consulting services.

The CEO of Deque Systems is Preety Kumar.


HTML-Kit is a proprietary HTML editor for Microsoft Windows made by chami.com.

The application is a full-featured HTML editor designed to edit, format, validate, preview and publish web pages in HTML, XHTML and XML -languages.

HTML-Kit is freeware, although extra features are available at a cost to registered users.

An Alpha version, HTML-Kit Tools (previously named build 300), is in development and is currently only available for download by registered users. Build 292, the current stable build is available for download as freeware.

IBM Home Page Reader

Home Page Reader (Hpr) was a computer program, a self-voicing web browser designed for people who are blind. It was developed by IBM from the work of Chieko Asakawa at IBM Japan.

The screen reader met World Wide Web Consortium (W3C) HTML 4.01 specifications, Web Content Accessibility Guidelines 1.0 and User Agent Accessibility Guidelines 1.0.In 2006, it was announced on the Hpr mailing list that IBM does not have plans for any further updates of HPR and the software was subsequently withdrawn from sale by IBM in December 2006. IBM has given code to be used as a Firefox extension.The program also had a peer-support mailing list.

Lisa Seeman

Lisa Seeman is an inventor and an entrepreneur and has been instrumental in creating standards for interoperability and accessibility.

She currently works for Athena ICT.

Meta refresh

Meta refresh is a method of instructing a web browser to automatically refresh the current web page or frame after a given time interval, using an HTML meta element with the http-equiv parameter set to "refresh" and a content parameter giving the time interval in seconds. It is also possible to instruct the browser to fetch a different URL when the page is refreshed, by including the alternative URL in the content parameter. By setting the refresh time interval to zero (or a very low value), meta refresh can be used as a method of URL redirection.

Mystery meat navigation

Mystery meat navigation (also known as MMN) is a disparaging term coined in 1998 by Vincent Flanders, author and designer of the website Web Pages That Suck, to describe a web page where the destination of the link is not visible until the user points their cursor at it. Such interfaces lack a user-centered design, emphasizing aesthetic appearance, white space, and the concealment of relevant information over basic practicality and functionality.The epithet "mystery meat" refers to the meat products often served in American public school cafeterias whose forms have been so thoroughly reprocessed that their exact types can no longer be identified by their appearances: like them, the methods of MMN are clear to the producer but baffling to the consumer.

Flanders originally and temporarily described the phenomenon as Saturnic navigation in reference to the Saturn Corporation, whose company website epitomized this phenomenon. Flanders writes, "The typical form of MMN is represented by menus composed of unrevealing icons that are replaced with explicative text only when the mouse cursor hovers over them".

PAS 78

PAS 78: Guide to good practice in commissioning accessible websites is a Publicly Available Specification published on March 8, 2006 by the British Standards Institution (BSI) in collaboration with the Disability Rights Commission (DRC). It provides guidance to organisations in how to go about commissioning an accessible website from a design agency. It describes what is expected from websites to comply with the UK Disability Discrimination Act 1995 (DDA), making websites accessible to and usable by disabled people


SortSite is a web crawler that scans entire websites for quality issues including: accessibility; browser compatibility; broken links; legal compliance; search optimization; usability and web standards compliance.

Tableless web design

Tableless web design (or tableless web layout) is a web design method eschewing the use of HTML tables for page layout control purposes. Instead of HTML tables, style sheet languages such as Cascading Style Sheets (CSS) are used to arrange elements and text on a web page.

URL redirection

URL redirection, also called URL forwarding, is a World Wide Web technique for making a web page available under more than one URL address. When a web browser attempts to open a URL that has been redirected, a page with a different URL is opened. Similarly, domain redirection or domain forwarding is when all pages in a URL domain are redirected to a different domain, as when wikipedia.com and wikipedia.net are automatically redirected to wikipedia.org. URL redirection is done for various reasons: for URL shortening; to prevent broken links when web pages are moved; to allow multiple domain names belonging to the same owner to refer to a single web site; to guide navigation into and out of a website; for privacy protection; and for hostile purposes such as phishing attacks or malware distribution.

US State Laws and Policies for ICT Accessibility

Many individual states within the US have accessibility policies for Information and Communications Technology (ICT). These policies often include references to national or international standards. They provide websites and software authors with technical details to ensure that users with disabilities can access the information and that adequate functionality is assured. The most commonly referenced standards are Section 508 and the W3C's Web Content Accessibility Guidelines. The table below provides information for all fifty states and indicates whether policies are in place for websites and software. It also indicates what standards the web policies are based on and provides links to the policies.


WebAIM (Web Accessibility in Mind) is a non-profit organization based at Utah State University in Logan, Utah. WebAIM has provided web accessibility solutions since 1999. WebAIM's mission is to expand the potential of the web for people with disabilities by providing the knowledge, technical skills, tools, organizational leadership strategies, and vision that empower organizations to make their own content accessible to people with disabilities.

Web Accessibility Initiative

The World Wide Web Consortium (W3C)'s Web Accessibility Initiative (WAI) is an effort to improve the accessibility of the World Wide Web (WWW or Web) for people with disabilities. People with disabilities may encounter difficulties when using computers generally, but also on the Web. Since people with disabilities often require non-standard devices and browsers, making websites more accessible also benefits a wide range of user agents and devices, including mobile devices, which have limited resources.

The W3C launched the Web Accessibility Initiative in 1997 with endorsement by The White House and W3C members. It has several working groups and interest groups that work on guidelines, technical reports, educational materials and other documents that relate to the several different components of web accessibility. These components include web content, web browsers and media players, authoring tools, and evaluation tools.

Web accessibility

Web accessibility is the inclusive practice of ensuring there are no barriers that prevent interaction with, or access to, websites on the World Wide Web by people with disabilities. When sites are correctly designed, developed and edited, generally all users have equal access to information and functionality.

For example, when a site is coded with semantically meaningful HTML, with textual equivalents provided for images and with links named meaningfully, this helps blind users using text-to-speech software and/or text-to-Braille hardware. When text and images are large and/or enlargeable, it is easier for users with poor sight to read and understand the content. When links are underlined (or otherwise differentiated) as well as colored, this ensures that color blind users will be able to notice them. When clickable links and areas are large, this helps users who cannot control a mouse with precision. When pages are not coded in a way that hinders navigation by means of the keyboard alone, or a single switch access device alone, this helps users who cannot use a mouse or even a standard keyboard. When videos are closed captioned or a sign language version is available, deaf and hard-of-hearing users can understand the video. When flashing effects are avoided or made optional, users prone to seizures caused by these effects are not put at risk. And when content is written in plain language and illustrated with instructional diagrams and animations, users with dyslexia and learning difficulties are better able to understand the content. When sites are correctly built and maintained, all of these users can be accommodated without decreasing the usability of the site for non-disabled users.

The needs that Web accessibility aims to address include:

Visual: Visual impairments including blindness, various common types of low vision and poor eyesight, various types of color blindness;

Motor/mobility: e.g. difficulty or inability to use the hands, including tremors, muscle slowness, loss of fine muscle control, etc., due to conditions such as Parkinson's disease, muscular dystrophy, cerebral palsy, stroke;

Auditory: Deafness or hearing impairments, including individuals who are hard of hearing;

Seizures: Photo epileptic seizures caused by visual strobe or flashing effects.

Cognitive and intellectual: Developmental disabilities, learning difficulties (dyslexia, dyscalculia, etc.), and cognitive disabilities of various origins, affecting memory, attention, developmental "maturity", problem-solving and logic skills, etc.

Web standards

Web standards are the formal, non-proprietary standards and other technical specifications that define and describe aspects of the World Wide Web. In recent years, the term has been more frequently associated with the trend of endorsing a set of standardized best practices for building web sites, and a philosophy of web design and development that includes those methods.

Will Creedle

Will Creedle (born April 16, 1973 in Rochester, Minnesota) is an American Software Quality Assurance Engineer and advocate for extending the Americans with Disabilities Act of 1990 to all title III websites. He is known for suggesting that conformance is crucial to good design because it brings context to content and accurately re-prioritizes the visual to reflect the content as opposed to the site serving the visuals. He has advocated that the time is now for companies to commit to web compliance, ahead of the DOJ regulations coming in 2018, as the DOJ has provided what their compliance standards will be for TITLE III companies: WCAG 2.0 Level AA of the Web Content Accessibility Guidelines.

Creedle spent 7 years working in Manhattan at R/GA, where he conceived the idea of the world's first tweeting e-cigarette as well as worked on several Clio, AD&D and Cannes Cyber Lion winning projects.

ZAC Browser

ZAC Browser (Zone for Autistic Children) is a discontinued web browser designed specifically for children and teenagers with autism and autism spectrum disorders such as Asperger syndrome, pervasive developmental disorders (PDD) and PDD-NOS.Because autistic children display characteristics such as impairments in social interaction, impairments in communication, restricted interests and repetitive behavior, the standard browser experience can often be overwhelming. The ZAC browser reduces the number of user interface controls and removes access to much of the Web in order to simplify the experience for autistic children.

ZAC was available as a free download for Windows 98/ME/2000/XP/Vista/7.

Products and
ISO standards by standard number

This page is based on a Wikipedia article written by authors (here).
Text is available under the CC BY-SA 3.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.