News

W3C Advances Web Accessibility Guidelines

The World Wide Web Consortium (W3C) has updated its set of recommendations for designing Web pages so they can easily accessed by those with disabilities.

Version 2.0 of the Web Content Accessibility Guidelines (WCAG) provides techniques to help prepare Web pages so they can be read by those who are blind, deaf or have cognitive limitations. Such users may use screen readers, Braille displays, audio text readers and other assistive technologies.

Released last week, version 2.0 updates the first version of the guidelines, published in 1999.

"Version 2.0 of the Web Content Accessibility Guidelines goes a long way toward promoting [the] goal of global harmonization of accessibility requirements," said David Capozzi, the U.S. Access Board executive director, in a statement. The Access Board hopes to further the goal in its rulemaking to update its [S]ection 508 standards in the coming year."

Section 508 of the Rehabilitation Act requires agencies to give disabled employees and members of the public equal access to all available information.

Developed by the W3C's Web Accessibility Initiative working group, the new version of the Web Content Accessibility Guidelines both simplifies and extends the first set of the recommendations. It divides the recommendations into four categories, each group aimed to make the Web page more:

  • Perceivable: This group of recommendations advises how to render Web pages in such a way that the content can be transposed into other formats, such as braille, large-type, or read-aloud.

  • Operable: This group of recommendations advises how to set up Web pages that they can be easily navigated.

  • Understandable: This group of recommendations offers tips on how to shape content so it can be easily understood.

  • Robust: This group of recommendations advises how to future-proof Web pages, as well as make them digestible by the widest possible range of assistive technologies.
In addition to the guidelines themselves, the W3C also offers a quick reference guide, a set of techniques for implementing the suggestions, and a document that details the recommendations in exhaustive detail.

About the Author

Joab Jackson is the chief technology editor of Government Computing News (GCN.com).

comments powered by Disqus

Featured

  • AI for GitHub Collaboration? Maybe Not So Much

    No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.

  • Visual Studio 2022 Getting VS Code 'Command Palette' Equivalent

    As any Visual Studio Code user knows, the editor's command palette is a powerful tool for getting things done quickly, without having to navigate through menus and dialogs. Now, we learn how an equivalent is coming for Microsoft's flagship Visual Studio IDE, invoked by the same familiar Ctrl+Shift+P keyboard shortcut.

  • .NET 9 Preview 3: 'I've Been Waiting 9 Years for This API!'

    Microsoft's third preview of .NET 9 sees a lot of minor tweaks and fixes with no earth-shaking new functionality, but little things can be important to individual developers.

  • Data Anomaly Detection Using a Neural Autoencoder with C#

    Dr. James McCaffrey of Microsoft Research tackles the process of examining a set of source data to find data items that are different in some way from the majority of the source items.

  • What's New for Python, Java in Visual Studio Code

    Microsoft announced March 2024 updates to its Python and Java extensions for Visual Studio Code, the open source-based, cross-platform code editor that has repeatedly been named the No. 1 tool in major development surveys.

Most   Popular

Subscribe on YouTube