Slide 27
Slide 27 text
1. Introduction
2. Editorial content
3. Images
4. Structure/function/layout
5. Audio and video content (A/V)
6. Forms
7. Documents
8. Links
9. Document history
Accessibility Guidelines v1.9
1. Introduction
2. Editorial content
BBC Guidelines
S&G Home
S&G About
Accessibility
Use of Colour
Flicker and Movement
Games
Keyboard Access
Multimedia
Accessibility
PDF Accessibility
Screen-Reader
Testing Guidelines
Self-voicing
Guidelines
Subtitling Guidelines
Text Equivalents
Text Links
Mobile Accessibility
Design & Editorial
Infrastructure
Policy
Red Button
Technical
Glossary
Contacts
This standard outlines the requirements and recommendations for making BBC websites accessible with
respect to editorial content and user experience. Other technical aspects of accessibility are covered in
the technical standards, e.g. Semantic Mark-up, CSS, Javascript, XHTML, etc. Other aspects of
accessibility are covered in separate standards, e.g. subtitles, use of colour, flicker and movement,
games, keyboard access, text equivalents, text links etc.
Top of page
2.1 You MUST provide an accessible alternative to any potentially inaccessible core content, including
all plug-in content, UNLESS this can be proven to be technically or practically impossible.
2.2 All accessible alternative content MUST be updated in line with and at the same time as the original
content.
2.3 You MUST provide an appropriate text equivalent for each non-text element of the core content. See
the Textual Equivalents Standard.
2.4 Where the language in the document changes (e.g. from English to Welsh), you MUST indicate this
with a tag containing a Lang attribute.
2.5 All text of more than two lines MUST be left aligned (if published language is naturally ranged left
e.g. English), except for tabular data and where the formatting is integral to the meaning of the text,
e.g. poetry.
2.6 You SHOULD use plain language and avoid jargon.
Sign in News Sport Weather iPlayer TV Radio More… Search
Search
DOCS EDITING DISCUSSION BLOG COMMUNITY ISSUES
HOME DOCS CONCEPTS ACCESSIBILITY
Web Platform Docs is currently in
Web Platform Docs is currently in alpha
alpha. Join our community of contributors and help
. Join our community of contributors and help
us reach
us reach beta!
See the Editor's Guide to learn how to get involved.
Are you skilled in CSS? Please help us reach our goal of
complete CSS property articles by July in our weekly Web Platform Wednesday !
Web accessibility basics
Summary
Accessibility is making the Web work for people with a diverse range of abilities. Accessibility is essential for
developers and organizations that want to create high quality websites and web tools, and not exclude people
from using their products and services. Accessibility is vital to enable people with disabilities to participate equally
on the Web. It is a legal requirement in some cases, and a best practice in all cases.
This page provides an overview of web accessibility and links to resources for more information. We suggest that
you read through this whole page first, then go back and follow the links to learn more.
The Web is for all people
The Web is fundamentally designed to work for all people, whatever their hardware, software, language, culture,
location, or physical or mental ability.
When the Web meets this goal, it is accessible to people with a diverse range of hearing, movement, sight, and
cognitive ability. Thus the impact of disability is radically changed on the Web because the Web removes barriers to
communication and interaction that many people face in the physical world.
However, when websites, web technologies, or web tools are badly designed, they can create barriers that exclude
people from using the Web. For example, an inaccessible website could:
prevent people who are deaf from getting information from a podcast or video
CONTENTS
Summary
The Web is for all people
What is web
accessibility?
Web accessibility is
essential for equal
opportunity
Understand how people
use the Web
Accessibility
requirements
ARIA
The components of web
accessibility
Web Content
Tools
People - web content
creators and web users
Business case
Older users
Mobile Web
Learn more from W3C
WAI
References and
acknowledgements
•
EDIT ▾
TOOLS ▾
LOG IN ▾
A Primer To Vestibular
Disorders
Key facts, definitions, demographics
and causes of vestibular disorders.
How–to: Use Skip
Navigation links
Use skip nav links to ease keyboard
user fatigue and frustration.
How–to: Use TITLE
attributes
Short answer: Avoid using title
attributes except in a few special
MYTH: Screen readers
don’t use JavaScript
98.6% of all screen readers have
JavaScript enabled.
Latest Posts
The Accessibility Project
The Accessibility Project
A community-driven effort to make web accessibility
A community-driven effort to make web accessibility
easier.
easier.
Learn more
Learn more
Learn more
Contribute on Github
Contribute on Github
Contribute on Github
A11Y Project
A11Y Project Archives
Archives Checklist
Checklist Resources
Resources About
About
The BBC are fantastic at sharing what they discover, their Standards are great, so is their Mobile guidance.
http://www.bbc.co.uk/guidelines/futuremedia/accessibility/
http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile_access.shtml
WebPlatform.org is getting better all the time. Same goes for a11yproject.com.
People like Jared Smith at WebAIM.org do a stellar job of documenting best practices,
we’ve made a start with ours in the Service Design Manual