Web Accessibility & ADA Archives - Capitol Tech Solutions https://www.capitoltechsolutions.com/blog/category/digital-marketing/web-accessibility-ada/ Tue, 30 Aug 2022 00:21:44 +0000 en-US hourly 1 https://wordpress.org/?v=6.6.1 https://www.capitoltechsolutions.com/wp-content/uploads/cropped-capitoltechsolutions-20years-favicon-32x32.png Web Accessibility & ADA Archives - Capitol Tech Solutions https://www.capitoltechsolutions.com/blog/category/digital-marketing/web-accessibility-ada/ 32 32 Common Website Accessibility & ADA Compliance Mistakes to Avoid https://www.capitoltechsolutions.com/blog/top-five-ada-website-mistakes/ Thu, 05 Aug 2021 21:55:48 +0000 https://www.capitoltechsolutions.com/?p=11449 The post Common Website Accessibility & ADA Compliance Mistakes to Avoid appeared first on Capitol Tech Solutions.

]]>

Common Website Accessibility & ADA Compliance Mistakes to Avoid

Headshot of Patrick
A label announcing top five with a bullhorn highlights the most common ADA compliance mistakes made by website developers.
Where do you start when you’re looking to optimize your business website’s accessibility? What’re the most important dos and don’ts?

We’ve narrowed it down to a top-five list of website accessibility standards that are commonly missing on even the most ADA-compliant websites.

We based our list on ADA audits conducted by Capitol Tech Solutions and the World Wide Web Consortium (W3C), the organization that publishes webpage guidelines so the internet can better serve people with disabilities.

A recap on the Web Content Accessibility Guidelines & ADA Compliance

The Web Content Accessibility Guidelines, WCAG, are a set of success criteria for testing how user-friendly your website is for people with disabilities. There are a few different iterations, with the most common being WCAG 2.0 AA and WCAG 2.1 AA. The former has 38 success criteria, and the latter has 50.

Federal and California state law requires government websites to comply with WCAG 2.1 AA, but the U.S. Department of Justice gives business websites a bit more leeway. Most private-sector webpages use WCAG 2.0 AA for ADA compliance.

In a separate blog, we explain WCAG best practices and the success criteria of WCAG 2.1.

Ensuring your business website meets these web accessibility standards will allow users with disabilities to have equal access online while using assistive technology. And having an accessible website will save you from a costly lawsuit.

Remember, businesses fall under Title III of the ADA, guaranteeing places of public accommodation provide equitable services.

We break down the importance of website accessibility and the potential legal repercussions you could face here.

Our certified web developers are experts in WCAG and ADA compliance. Contact us today for an ADA audit of your website.

Contact Us

Our Top Five ADA Website Compliance Mistakes

1. Missing or poor alternative text on images

People with eyesight-related disabilities rely heavily on screen readers to dictate webpages to them.

A common feature on webpages is an accompanying picture, just like on this blog post. Assistive technology cannot yet scan and describe images to users, so web developers (like those here at CTS) add alternative descriptions, also known as alt text.

When writing alt text, you have to keep in mind the context and character count. The optimal character count to ensure screen readers correctly relay an alt text should be fewer than 125 characters. Basically, as long as the previous sentence, which came in at 118 characters.

The context you fit into the restrictive character count is the most crucial aspect of this digital accessibility rule. To write a successful and inclusive alt text, you should:

  • Be specific in your description. Start with the subject or setting.
  • Add context based on the topic of the webpage. This blog is about ADA compliance, and our alt text reflects that.
  • Don’t start a description with “picture of” or anything similar. Assistive technologies will be able to determine a picture based on the website’s HTML coding.

2. Insufficient Color Contrast

Font and background color combinations with low contrast can be problems for people with low vision or color blindness.

WCAG 2.0 Level AA requires a contrast ratio of 4.5 to 1 for standard text and 3 to 1 for large text (14 point font, bold or larger).

You might be wondering what precisely a contrast ratio is. Well, when used for ADA compliance, it means the brightness of a completely white image is 4.5 times brighter than a completely black image (or three times brighter for large, bold text).

Text included in your logo is one of the few exceptions to this rule.

3. Keyboard Access

Users with motor or visual impairments opt for keyboard navigation to browse websites.

A quick way to check if your website’s architecture supports keyboard-only use is to tap the tab key while on your website. If the content is surrounded by a visible outline, like the blue box on our website, then you’ve passed. The visual indication informs users of their location on the page.

Often, website creators disable the default indicator for design esthetics. You should avoid doing this or rectify this soon after discovery. Keyboard focus should be visible and follow a logical order through the webpage to comply with ADA standards.

4. Meaningful Link Text

One of the first things people who use a screen reader do is pull up a list of links and navigate through that list. With that in mind, link text should be able to stand alone, independent of its context.

Descriptive and meaningful links help users choose which links they want to follow easily. Pages with links should provide enough detail that allows for a cursory understanding of what content to expect while they search your site.

You can design ambiguous links like “Click here” or “Read more” to include a summary of the pages they lead to.

Also, speech recognition users can click links with a voice command like “click” followed by the link text. So, it’s helpful to keep link text short and easy to say.

5. Landmark Roles

People with normal vision can quickly review a webpage or document and find the content they’re interested in, and if these users can click a mouse, they can click on a link or other control on the page.

But for users with disabilities, who primarily use keyboards, screen readers, and other assistive technologies, developers need to use landmarks representing a block of content.

Accessible Rich Internet Applications (ARIA) allow rich, interactive user interfaces to be more accessible.

There are eight of these roles, each representing a block of content commonly on webpages. To use them, add a relevant role attribute to an appropriate container within your HTML. Then, users with assistive technologies can quickly jump to that section of the page.

The eight ARIA landmark roles are:

  • role=”banner”
  • role=”navigation” (such as a menu)
  • role=”main” (the main content of the page)
  • role=”complementary” (such as a sidebar)
  • role=”contentinfo” (meta data about the page like a copyright statement)
  • role=”search”
  • role=”form”
  • role=”application” (a web application with its own keyboard interface)

Take the first step toward ADA compliance by contacting our ADA & WCAG experts.

Contact Us

CTS Celebrates 31st Anniversary of Americans with Disabilities Act

Capitol Tech Solutions marked the 31st anniversary of the Americans with Disabilities Act with a month-long web content campaign promoting ADA website compliance.

Leading up to the July 26 anniversary date, we published comprehensive reports on the importance of equitable web browsing for the business and government communities.

“Digital accessibility has become increasingly important as technology continues to advance,” said Capitol Tech Solutions’ CEO Bobby Reed. “I’m proud of the work we’ve done to make the websites of our government and business clients more inclusive for everyone.”

Signed into law by President George H.W. Bush in 1990, the Americans with Disabilities Act prohibits discrimination based on disabilities and guarantees equitable treatment in public accommodation, employment, transportation, and community living.

The U.S. Department of Justice, federal and state court cases have expanded the meaning of public accommodation to include government and business websites.

People with disabilities interact with websites through assistive technologies, such as screen readers, alternative keyboards or switches, braille and refreshable braille, screen magnifiers, sound notification, scanning software, voice recognition, and more.

The User Experience Team at Capitol Tech Solutions ensures the company’s web clients meet ADA website compliance standards.

Through the Section 508 Amendment to the Rehabilitation Act of 1973, the federal government requires all national electronic information to be accessible to people with disabilities. This mandate extends to existing or new government websites and uses WCAG as the standard.

Contact Our Team

Don’t know where to start or can’t find the local talent you need to launch your new digital endeavor? Let our team of experienced professionals help you map out your next project or fix an existing one.

[contact-form-7]

Related Articles

The post Common Website Accessibility & ADA Compliance Mistakes to Avoid appeared first on Capitol Tech Solutions.

]]>
What are the Web Content Accessibility Guidelines? https://www.capitoltechsolutions.com/blog/ada-requirements-business-websites/ Mon, 26 Jul 2021 22:34:10 +0000 https://www.capitoltechsolutions.com/?p=11334 The post What are the Web Content Accessibility Guidelines? appeared first on Capitol Tech Solutions.

]]>

What are the Web Content Accessibility Guidelines?

Headshot of Patrick
A web developer sits in front of a laptop typing HTML code to improve website accessibility for people with disabilities.
How well your business or government website and content conforms to the Web Content Accessibility Guidelines, WCAG, determines if it’s compliant with the Americans with Disabilities Act.

In broad terms, WCAG is the standard published by the World Wide Web Consortium (W3C) as part of the group’s Web Accessibility Initiative, more on that in a moment.

There are different versions of WCAG, each with varying levels of conformance: Level A, Level AA, and Level AAA. To make your website digitally accessible, developers (like ours here at Capitol Tech Solutions) will help you comply with WCAG 2.0 AA and WCAG 2.1 AA. Worldwide, WCAG 2.0 AA is the most-used standard.

What’s the difference between version 2.0 and version 2.1? WCAG 2.0 AA has 38 success criteria, and WCAG 2.1 AA has 50 success criteria. The requirements are essentially to-do lists that will make your website easier to use for people with disabilities and save you from a compliance lawsuit.

In another blog post, we explain why your business website should be ADA compliant.

Need help to understand the Web Content Accessibility Guidelines? Our web developers are certified in ADA compliance standards.

Contact Us

What About Overlay Widgets? Will that solve my ADA Compliance Issue?

If you’re looking for a quick fix to ADA compliance, we at Capitol Tech Solutions are here to tell you there isn’t one.

Whether you’re getting started with a new business website or you’ve received a letter threatening an ADA compliance lawsuit, an ad promising an overlay widget that will solve your problem sounds like a godsend, but it’s merely snake oil.

These widgets don’t change your website’s code or content to be accessible and conform to WCAG. Instead, you’ll get a JavaScript menu that lays over your website when it’s activated.

When a person with a disability activates the overlay widget, it forces them to have a different experience than normal users would.

And a separate and unequal experience is an explicit violation of the ADA.

ADA Maintenance of Your Business Website

OK, so you’ve built an ADA-compliant business website (or had our web designers help you create one). Now what? Like how a car needs its oil changed, you need to perform preventative maintenance to ensure you don’t receive an ADA Website Compliance demand letter from a law firm.

It’s a good idea to schedule periodic accessibility checks to ensure your content stays digitally accessible, either through automated or manual testing. As developers deploy updates to browsers, devices, and assistive technologies, it will change how users interact with your website.

Launching new webpages and products, or updating site navigation or functionality, is also an optimal time to test for website accessibility and ADA compliance.

The Full Breakdown of WCAG 2.0 & WCAG 2.1

The overall goal of The World Wide Web Consortium (W3C) is to publish standards that make the web more uniform so it can run more efficiently.

W3C initially released WCAG 2.0 in 2008, with the WCAG 2.1 update arriving in 2018. The W3C is in the final stages of publishing WCAG 2.2 this year. The group continually refines its guidelines and success criteria to ensure websites are more inclusive for users with disabilities.

WCAG Website Compliance Standards

The W3C uses four principles to determine guidelines for web accessibility:

  • Perceivable
  • Operable
  • Understandable
  • Robust

Under these four principles are a group of guidelines, which directly inform WCAG success criteria.

  • Perceivable
    • Provide text alternatives for non-text content
    • Provide captions and other alternatives for multimedia
    • Create content that can be presented in different ways, including assistive technologies, without losing meaning
    • Make it easier for users to see and hear content
  • Operable
    • Make all functionality available from a keyboard
    • Give users enough time to read and use content
    • Do not use content that causes seizures or physical reactions
    • Help users navigate and find content
    • Make it easier to use inputs other than a keyboard
  • Understandable
    • Make text readable and understandable
    • Make content appear and operate in predictable ways
    • Help users avoid and correct mistakes
  • Robust
    • Maximize compatibility with current and future user tools

Think of the guidelines as goals. The WCAG success criteria are the tools to meet these goals.

Our User Experience web developers are certified in ADA compliance. Let our team test your website’s level of compliance.

Contact Us

What Are WCAG Success Criteria? How Do I Meet These Standards?

WCAG 2.0 and WCAG 2.1 break down each guideline into success criteria used for testing your website’s level of compliance.

As mentioned earlier, there are three degrees of WCAG compliance: Level A, Level AA, and Level AAA. Each is progressively harder than the last. This blog post will highlight WCAG 2.1 AA, as its the standard required under federal and California state law for government websites.

Requirements to meet WCAG are very technical, even when your User Experience team specializes in bringing clients into compliance with the ADA.

If the summary of principles and guidelines didn’t answer your questions, our comprehensive, expandable list below provides a more thorough explanation based on W3C published reports outlining all 50 WCAG 2.1 AA success criteria.

Text Alternatives

  • Non-Text Content: All non-text content presented to a user must have a text alternative that serves the equivalent purpose.

Time-based Media

  • Prerecorded Video-Only & Audio-Only: There must be an alternative for time-based media available to users that presents equivalent information, such as a text transcript, animation, or descriptive audio track.
  • Prerecorded Captions: Developers must provide captions for all prerecorded audio content in synchronized media, such as webcasts, press conferences, and online training presentations.
  • Prerecorded Audio Description or Media Alternative: There must be an alternative for time-based media or audio descriptions of the prerecorded video content provided for synchronized media, such as descriptions in existing pauses in dialogue or presenting information in text form.
  • Live Captions: Developers must provide captions for all live audio content in synchronized media.
  • Prerecorded Audio Description: Developers must provide audio descriptions for all prerecorded video content in synchronized media.

Adaptable

  • Info and Relationships: Information, structure, and relationships conveyed through a website’s presentation must be determinable by assistive technologies or available in text.
  • Meaningful Sequence: When the sequence of content affects its meaning, a correct reading sequence must be determinable by assistive technologies.
  • Sensory Characteristics: Developers must provide instructions for understanding and operating content without using sensory characteristics as determiners, such as shape and position.
  • Orientation: Content does not restrict its view and operation to a single display orientation, i.e., portrait or landscape, unless deemed essential.
  • Identify Input Purpose: Input fields, such as email and password logins, must be programmed to state what type of information is being requested and for what purpose the user will use it.

Distinguishable

  • Use of Color: Color must not be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
  • Audio Control: If any audio on a webpage plays automatically for more than three seconds, there must be an option to pause or stop the audio or a tool to control audio volume independently from the overall system volume.
  • Minimum Contrast: The text’s visual presentation and images must have a contrast ratio of at least 4.5:1. Some exceptions apply.
  • Resize Text: Except for captions and images of text, text must be resizable without assistive technology up to 200 percent without the loss of content or functionality.
  • Images of Text: Users must adjust the text presentation as needed, including font size, foreground and background color, font family, line spacing, and alignment.
  • Reflow: Developers must present content without the loss of information or functionality and the requirement of scrolling in two dimensions.
  • Non-Text Contrast: The visual presentation of user interface components and graphical objects must have a contrast ratio of at least 3:1 against adjacent colors.
  • Text Spacing: Content must support the ability to increase spacing between lines, words, letters, and paragraphs to assist a user with effectively reading text.
  • Content on Hover or Focus: This condition ensures that additional content does not interfere with viewing or operating a webpage’s original content.

Keyboard Accessible

  • Keyboard: All functionality of the content must be operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just endpoints.
  • No Keyboard Trap: Content must not “trap” keyboard focus within a subsection of content on a webpage, such as a dialogue box that forces users into clicking “cancel” or “OK” buttons.
  • Character Key Shortcuts: Users must be able to turn off or reconfigure shortcuts that are made up of only character keys to reduce accidental activation of keyboard shortcuts.

Enough Time

  • Timing Adjustable: Webpages must provide options to disable time limits, customize the length of time limits, or request more time before a time limit occurs to help users who require more time to complete tasks. An example is a webpage that cycles through the latest headlines in a rotating fashion. There must be an interactive control that allows the user to extend the length of time between each update.
  • Pause, Stop, Hide: For moving, blinking, or scrolling information, users must be able to pause, stop, or hide it. For auto-updating information, users must be able to pause, stop, or hide it or control the frequency of the update.

Seizures & Physical Reactions

  • Three Flashes or Below Threshold: Webpages must not contain anything that flashes more than three times in any one second period.

Navigable

  • Bypass blocks: Users must be able to bypass blocks of content repeated on multiple webpages, such as navigation links, heading graphics, and advertising frames.
  • Page Titled: Webpages have titles that describe the topic or purpose.
  • Focus Order: Users must be able to navigate sequentially through content to encounter information in an order that is consistent with the meaning of the content. Users must be able to operate sequentially from a keyboard.
  • In Context Link Purpose: The purpose of each link must be determined from the link text alone or from the link text together with its programmatically determined link context, such as a “read more” link on a webpage with multiple news articles.
  • Multiple Ways: There must be more than one way to locate a webpage within a set of webpages, except where the webpage is the result of, or a step in, a process, such as a search mechanism.
  • Headings & Labels: Headings and labels describe the topic or purpose.
  • Focus Visible: Any keyboard-operable user interface has a mode of operations where the keyboard focus indicator is visible. An example would be displaying a vertical bar within a text field, indicating to the user that they can insert text.

Input Modalities

  • Pointer Gestures: All functionally must allow people with disabilities to use multipoint or path-based gestures for operation with a single pointer without a path-based gesture. An example would be a website with a map view supporting the pinch gesture zoom into the map content.
  • Pointer Cancellation: Measures must be in place to allow users to abort or undo accidental pointer input. An example would be allowing the user to load a new page or follow a link when they release a mouse pointer or lift their finger from a touchscreen (called an Up-Event activation).
  • Label in Name: For user interface components with labels that include text or images of text, the name contains the visually presented text.
  • Motion Actuation: Users must have the ability to disable functionalities operated by device motion or user motion functionalities to prevent accidental actuation.

Readable

  • Language of Page: The developer must determine the default human language of each webpage for assistive technologies to read the text more accurately.
  • Language of Parts: The human language of each passage or phrase in the content must be determinable by assistive technologies to accurately switch between multiple languages.

Predictable

  • On Focus: When any user interface component receives focus, it does not initiate a change of context, such as a drop-down menu that allows users to choose between webpage destinations by pressing one key while maintaining the ability to navigate between options with other keystrokes.
  • On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the interface advises the user of the behavior before using the component, such as entering text into a text field or checking a checkbox.
  • Consistent Navigation: Repeated content on multiple webpages must appear in the same relative order upon each repeat unless the user initiates a change.
  • Consistent Identification: Components with the same functionality within a set of webpages must be identified consistently, such as a search function.

Input Assistance

  • Error Identification: If an input error is automatically detected, the webpage must identify the error item so that the error can be described to the user in a text that assistive technologies can interpret.
  • Labels or Instructions: Developers must provide labels or instructions when content requires user input.
  • Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the recommendations are provided to the user.
  • Legal, Financial, Data Error Prevention: Users must be able to confirm or cancel the entry of legal, financial, or personal information, such as displaying an intermediary confirmation page that displays entered information.

Compatible

  • Parsing: Developers must ensure that webpages have complete start and end tags and are nested according to specification so that assistive technologies can parse the content accurately and without crashing.
  • Name, Role, Value: Developers must ensure that webpages provide role, state, and value information on all user interface components to enable compatibility with assistive technology. An example of this is Accessible APIs.
  • Status Messages: Status messages must be programmed to interact with assistive technologies, such as after a user presses an “Add to Shopping Cart” button, a section of content near the Shopping Cart icon adds the text “5 items.” A screen reader announces “Five items” or “Shopping cart, five items” to the user.

Contact Our Team

Don’t know where to start or can’t find the local talent you need to launch your new digital endeavor? Let our team of experienced professionals help you map out your next project or fix an existing one.

[contact-form-7]

Related Articles

The post What are the Web Content Accessibility Guidelines? appeared first on Capitol Tech Solutions.

]]>
What Does ADA Compliance Mean for a Business Website? https://www.capitoltechsolutions.com/blog/ada-compliance-business-websites/ Fri, 16 Jul 2021 21:46:59 +0000 https://www.capitoltechsolutions.com/?p=11233 The post What Does ADA Compliance Mean for a Business Website? appeared first on Capitol Tech Solutions.

]]>

What Does ADA Compliance Mean for a Business Website?

Headshot of Patrick
A blind person uses a computer with a braille display assistive device meant for persons with visual disabilities.
When you think of ADA compliance, what typically comes to mind? Accessibility requirements for brick-and-mortar public buildings, right? But what about websites?

A quick history lesson first: the Americans with Disabilities Act of 1990 is a civil rights law prohibiting discrimination based on disabilities. It imposes accessibility standards on places of public accommodation, which websites fall under, to guarantee equal access for people with disabilities.

If you manage a federal or state agency website, your website must be ADA compliant. But it’s a slightly different story for business websites.

Not all business websites fall under ADA guidelines mandating accessibility. However, it’s still the best practice to have an ADA-compliant website. Ensuring your website and web content are digitally accessible will save you the headache of receiving an ADA Website Compliance demand letter or lawsuit.

Not sure if your business’ website is ADA-compliant? Contact our User Experience team for an ADA website audit. We have the tools to make your website accessible.

Contact Us

What websites are mandated to be ADA compliant?

Technically speaking, accessibility requirements only extend to websites that affect interstate commerce and generally fall into 12 different categories:

  • An inn, hotel, motel, or other places of lodging.
  • A restaurant, bar, or other establishment serving food or drink.
  • A motion picture house, theater, concert hall, stadium, or other places of exhibition entertainment.
  • An auditorium, convention center, lecture hall, or other places of public gathering.
  • A bakery, grocery store, clothing store, hardware store, shopping center, or other sales or rental establishment.
  • A laundromat, dry-cleaner, bank, barbershop, beauty shop, travel service, shoe repair service, funeral parlor, gas station, office of an accountant or lawyer, pharmacy, insurance office, professional office of a healthcare provider, hospital, or other service establishments.
  • A terminal, depot, or other station used for specified public transportation.
  • A museum, library, gallery, or other places of public display or collection.
  • A park, zoo, amusement park, or other places of recreation.
  • A nurse, elementary, secondary, undergraduate, or postgraduate private school, or other educational places.
  • A daycare center, senior citizen center, homeless shelter, food bank, adoption agency, or other social service center establishment.
  • A gymnasium, health spa, bowling alley, golf course, or other places of exercise or recreation.

However, as your goal is to avoid a long, drawn-out, and technical legal battle, it’s best to make your website accessible from the very beginning.

The more commercial your website is, the more likely you are to be sued.

The exact phrasing used in Title III of the Americans with Disabilities Act states: “the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation.”

Why focus on website accessibility?

There isn’t a definitive federal law on the books addressing commercial web accessibility, requiring U.S. courts and the Department of Justice to step in and expand the meaning of Title III (public accommodations) to include websites.

Attorneys representing plaintiffs seeking equal web accessibility may target your website because it’s simply on the web. These law firms specifically seek a business page that does not conform to the ADA standards known as the Web Content Accessibility Guidelines (WCAG) 2.0 or 2.1 Level AA success criteria.

Common tactics used by law firms:

  • Pick a consumer-facing industry
  • Pull a list of all the companies within that industry
  • Run a web crawler on the homepage of each company
  • Send out a form demand letter with a summary of the web crawler findings
  • File a batch of lawsuits

Legal precedents used by plaintiffs:

  • The ADA is a liability law, meaning there is no room for excuses/defenses for violations.
  • The Unruh Civil Rights Act, a California law similar to the ADA, is often cited in attorney demand letters as it offers more damages to plaintiffs.
  • Legal groups use the Fair Housing Act and other anti-discrimination laws to sue website owners and target specific industries.
  • Employing fewer than 15 people does not exempt you from ADA compliance as a place of public accommodation.

How does the Department of Justice define accessibility?

The Department of Justice uses WCAG 2.0 and WCAG 2.1 to define digital accessibility but has not specified technical requirements in a final rule, so you have some flexibility in the matter.

The law does not mandate WCAG compliance for business websites (although California AB 434 requires all state departments to provide equal access). WCAG is a list of guidelines published by the World Wide Web Consortium (W3C) under their Web Accessibility Initiative.

The W3C publishes best practices to make the internet more uniform and run better, including the standardization of accessibility.

There are two versions of WCAG: WCAG 2.0 AA and WCAG 2.1 AA. The difference comes down to the number of success criteria, amounting to 38 for the former and 50 for the latter.

In another blog, we explain in-depth what the digital accessibility requirements entail.

Our certified web designers know how to make your organization’s website meet WCAG success criteria.

Contact Us

How Do People with Disabilities Use a Website?

Limitations related to sensory, physical, or cognitive functioning can affect how users interact with websites. Disabilities can be injury- or age-related conditions.

People with disabilities use assistive technologies to browse the internet, which pages should be coded to interact with seamlessly.

Some assistive technologies rely on the output of graphical desktop browsers, text browsers, voice browsers, multimedia players, and plug-ins to relay a website’s information to users.

A well-known assistive technology is screen reader software, which interprets what is displayed on screen to a speech synthesizer.

Other assistive technology includes:

  • Alternative keyboards or switches
  • Braille & Refreshable Braille
  • Screen magnifiers
  • Sound notification
  • Scanning software
  • Voice recognition

CTS Web Developers Pursue Certification in Section 508

At Capitol Tech Solutions, we enroll our web developers in accessibility training to better serve our clients. Che-Hung Liu, a graphic designer and web developer who’s been with the company since 2016, has completed several courses offered by the GSA Government-wide IT Accessibility Program.

If you choose to partner with CTS, Che will use industry-leading techniques from his Section 508 accessibility courses to bring your website into compliance, either in the private or public sectors.

Section 508 is the federal law requiring government agencies to make their websites accessible to people with disabilities.

Improve your users’ experience. We’ll test and make suitable accommodations on your website for ADA compliance.

Contact Us

Contact Our Team

Don’t know where to start or can’t find the local talent you need to launch your new digital endeavor? Let our team of experienced professionals help you map out your next project or fix an existing one.

[contact-form-7]

Related Articles

The post What Does ADA Compliance Mean for a Business Website? appeared first on Capitol Tech Solutions.

]]>