{"id":161,"date":"2022-04-21T08:43:43","date_gmt":"2022-04-21T05:43:43","guid":{"rendered":"https:\/\/www.accessi.org\/blog\/?p=161"},"modified":"2022-04-25T08:51:15","modified_gmt":"2022-04-25T05:51:15","slug":"web-accessibility-101","status":"publish","type":"post","link":"https:\/\/www.accessi.org\/blog\/web-accessibility-101\/","title":{"rendered":"Web Accessibility 101 – an Introduction"},"content":{"rendered":"

What is Web Accessibility?<\/h2>\n

Accessibility (or A11y for short) is the process of making websites, web applications, and digital products that all audiences, including disabled people, can access.<\/p>\n

A website is accessible when disabled people can complete tasks and operate the website’s functionality.<\/p>\n

The goal of accessibility is to create an inclusive web for all users. To achieve this goal, it is essential to consider temporary and permanent motor, cognitive, visual, auditory, speech, and neurological disabilities.<\/p>\n

The disabilities can be permanent, temporary, or situational.<\/p>\n

Why is Web Accessibility Important?<\/h2>\n

Accessibility is often an afterthought and not treated as an essential part of the web development process. However, you should adopt an accessibility-first approach when creating content for the web.<\/p>\n

Accessibility improves the ease of access to web content for people with and without disabilities. By building accessible websites, you end up creating a better experience for all your users. Everyone benefits from an accessible web.<\/p>\n

A World Bank report on disabilities<\/a> stated that 15% of people experience some form of disability, and an even more significant percentage is living with short-term functional difficulties.<\/p>\n

Web Accessibility ensures that these individuals can access your digital service, which<\/p>\n

There are legal and economic reasons for the importance of accessibility.<\/p>\n

Legal Importance of Web Accessibility<\/strong><\/p>\n

Legally, having an inaccessible website increases the chances of you paying a fine or facing legal issues such as lawsuits.<\/p>\n

Governments have put laws in place to protect disabled people and ensure that websites adhere to accessibility standards. Section 508 of the US Rehabilitation Act<\/a> requires that all electronic and information technology developed, maintained, or used by the federal government be accessible to people with disabilities.<\/p>\n

A Supreme Court ruling<\/a> allows blind users to sue retailers if their sites are not accessible.<\/p>\n

An Accessibility<\/a> report states that 2,352 web accessibility lawsuits were filed against U.S businesses in 2021.<\/p>\n

With the rise in accessibility-related lawsuits, it is in your best interest to have an accessible website to minimize legal risks.<\/p>\n

Economic Importance of Web Accessibility<\/strong><\/p>\n

The global disability market is estimated to be nearly $7 trillion.<\/p>\n

Economically, failure to cater to the disabled community means ignoring millions of potential customers with billions in purchasing power. The purchasing power of assistive-technology Internet users in the UK is $274 billion (2020 estimate<\/a>).<\/p>\n

\"An
An infographic of the purchasing power of disabled people in the UK<\/em><\/figcaption><\/figure>\n

A 2021 Forbes article<\/a> estimated that retailers were set to lose $828 Million in Christmas sales due To inaccessible websites.<\/p>\n

Web accessibility raises the SEO score of your website, boosting your traffic and visibility on search engines.<\/p>\n

Accessibility increases the number of potential customers you attract and the more your business grows.<\/p>\n

It is clear that having accessibility compliant websites is essential and beneficial.<\/p>\n

Web Accessibility Principles<\/h2>\n

Web accessibility is organized around four core principles called POUR principles. POUR is an acronym that stands for Perceivable, Operable, Understandable, Robust.<\/p>\n

Perceivable<\/strong>
\nThe first letter in the POUR acronym stands for Perceivable.
\nThe information must be presented in a format that users can perceive with their senses. For example, for deaf users or users hard of hearing, videos must have subtitles, and audios must have transcripts.<\/p>\n

Operable<\/strong>
\nThe second letter is O, which stands for Operable.
\nMany users with disabilities cannot use a website with a mouse. A website is operable when users can use various tools to operate them. Examples of these tools are keyboards, voice recognition software, and touchscreen.<\/p>\n

Understandable<\/strong>
\nThe third letter, U, stands for Understandable.
\nAn understandable website is one where both the information on the website and its user interface are clear to all users. Users will find a website with a proper structure and visual layout understandable. Adding charts and graphs where relevant also makes comprehension easier.<\/p>\n

Robust<\/strong>
\nThe last letter in the POUR acronym stands for Robust.
\nA robust website is accessible on multiple devices and platforms, including assistive technologies. Content must remain accessible even as technology and user agents evolve.<\/p>\n

Disabilities and Assistive Technologies<\/h2>\n

Assistive technology is any device, software program, equipment, product, or tool people with disabilities use to improve their performance. It promotes participation and inclusion of the elderly or people with disabilities.<\/p>\n

There are general-purpose assistive technologies such as wheelchairs, walkers, crutches, prosthetic devices, canes, scooters, spectacles, hearing aids, etc.<\/p>\n

Asides from general purpose assistive technologies, there are those for interacting with websites.<\/p>\n

Screen Readers<\/strong>
\nScreen readers are software used by blind or visually disabled people to read the content on the computer screen. They enable users to interact with web content in a non-visual manner.<\/p>\n

\"Screen
Screen Readers<\/em><\/figcaption><\/figure>\n

Braille<\/strong>
\nBraille is a system of touch reading for blind and visually impaired people. It is a system of raised dots that represent the letters of the alphabet.<\/p>\n

\"Braille\"
Braille<\/em><\/figcaption><\/figure>\n

Screen magnification software<\/strong>
\nThese are computer software that enlarges everything on a computer screen. They often come pre-packaged into computer systems.<\/p>\n

Alternative input devices<\/strong>
\nSome users may be unable to use a mouse or keyboard to work on a computer. They can use alternative input devices such as Head pointers, motion tracking or eye-tracking devices, single switch entry devices, large-print, and tactile keyboards, and Speech input software.<\/p>\n

\"A
A head pointer<\/em><\/figcaption><\/figure>\n

What exactly are ARIA Labels?<\/h3>\n

ARIA stands for Accessible Rich Internet Applications. It is a set of attributes you can add to HTML elements that define ways to make web content and applications more accessible to assistive technologies.<\/p>\n

ARIA labels come in when native HTML elements won\u2019t do the job. For example, cases where you need a popup menu or want to create a custom checkbox.<\/p>\n

ARIA labels allow you to specify attributes that modify how screen readers translate elements into the accessibility tree.<\/p>\n

Take the example of a custom checkbox below:<\/p>\n

\r\n<li tabindex=\"0\" class=\"checkbox\" checked>\r\n  Receive promotional offers\r\n<\/li>\r\n<\/pre>\n
While this works well for sighted users, screen readers will be unable to tell that this element is a checkbox.<\/p>\n
We can add ARIA attributes to the element to help screen readers identify the element as a checkbox:<\/p>\n
\r\n<li tabindex=\"0\" class=\"checkbox\" role=\"checkbox\" checked aria-checked=\"true\">\r\n  Receive promotional offers\r\n<\/li>\r\n<\/pre>\n
ARIA can modify the semantics of native HTML elements or add semantics to custom elements where no semantics exist.<\/p>\n
ARIA only gives more information to screen readers so they can interpret the DOM correctly. They do not change the behavior of elements.<\/p>\n
How to create Accessible Styling<\/h3>\n
How you style your websites significantly affects their accessibility. Besides using the proper HTML elements, the CSS styles you apply must also drive the website\u2019s accessibility.<\/p>\n
Here are some CSS accessibility tips:<\/p>\n
– Use legible font sizes and font types.
\n– Your headings should be bold and distinct from the body text.
\n– Your text color should work well with your background color.
\n– Create different styles for the hover, focus, and active states of link tags and form elements.
\n– Your website should be responsive and scale well when magnified.
\n– Always use fluid typography as this enables the user to change the font size to fit their needs.<\/p>\n
Let\u2019s see an example of how to style a button in an accessible manner.<\/p>\n
First, we define some basic styles for a button.<\/p>\n
\r\nbutton {\r\npadding: 1rem;\r\nwidth: 200px;\r\nfont-size: 1.3rem;\r\nborder-radius: 6px;\r\ncursor: pointer;\r\n}\r\n<\/pre>\n
\"Not
Not accessible button<\/em><\/figcaption><\/figure>\n
While the distinction between the button and the background is clear for sighted users, others will be unable to tell the difference.<\/p>\n
We can fix that by changing the value of the button\u2019s `background-color` property to color with better contrast.<\/p>\n
\r\nbutton {\r\npadding: 1rem;\r\nwidth: 200px;\r\nfont-size: 1.3rem;\r\nborder-radius: 6px;\r\nbackground-color: #cc9ef5;\r\ncursor: pointer;\r\n}\r\n<\/pre>\n
\"Accessible
Accessible button<\/em><\/figcaption><\/figure>\n
Now we have an accessible button.<\/p>\n
Conclusion<\/h3>\n
Web accessibility is an integral aspect of web development.<\/p>\n","protected":false},"excerpt":{"rendered":"
The goal of web accessibility is to create an inclusive web for all users. To achieve this goal, it is essential to consider temporary and permanent motor, cognitive, visual, auditory, speech, and neurological disabilities.<\/p>\n","protected":false},"author":2,"featured_media":201,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/posts\/161"}],"collection":[{"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/comments?post=161"}],"version-history":[{"count":17,"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/posts\/161\/revisions"}],"predecessor-version":[{"id":233,"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/posts\/161\/revisions\/233"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/media\/201"}],"wp:attachment":[{"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/media?parent=161"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/categories?post=161"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.accessi.org\/blog\/wp-json\/wp\/v2\/tags?post=161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}