Accessibility Considerations - tawana0518/mywebclass-simulation GitHub Wiki

Accessibility refers to ensuring that the webpage is designed and developed in a way that allows all users, including those with disabilities or limitations, to access the content and use the website effectively. This could include:

  • Providing alternative text for images: Users with visual impairments may rely on screen readers to access webpage content. Alternative text (alt text) provides a description of images, which is read by screen readers to help users understand the content of the images.

  • Using descriptive link text: Users with disabilities may navigate webpages using only the keyboard, rather than a mouse. Descriptive link text helps these users understand where links will take them and why they should click on them.

Later research:

*Ensuring proper contrast: Users with visual impairments may have difficulty seeing text if there is not enough contrast between the text and background. Ensuring proper contrast makes it easier for all users to read and understand the content on the webpage.

*Providing captions and transcripts for multimedia content: Users with hearing impairments may rely on captions or transcripts to understand audio or video content on the webpage.

*Structuring content with headings: Screen readers use headings to navigate the structure of a webpage. Structuring content with headings makes it easier for users with disabilities to understand the organization of the content.

These are just a few examples of accessibility considerations for a basic webpage. It's important to ensure that your website is accessible to all users, regardless of their abilities or limitations.

Business and legal Requirements for Accessibility:

*Compliance with Laws and Standards: Businesses must ensure that their websites are in compliance with laws and accessibility standards, such as the Americans with Disabilities Act (ADA)

*Non-Discrimination: Websites must be designed and developed in a way that does not discriminate against people with disabilities.

  • Accessible Design: Websites must be designed with accessibility in mind, including using proper color contrasts, providing alternative text for images and videos, and ensuring that the website is navigable with a keyboard.

*Accessibility Policy: Businesses should have an accessibility policy that outlines their commitment to accessibility.

By addressing these requirements, Ensure that the accessibility of MyWebClass.Org, making it more usable for individuals with disabilities and those using assistive technologies.

Add aria-* attributes: Provide more information to assistive technologies by adding appropriate aria-* attributes to elements like the navigation menu and other interactive components.

Ensure proper keyboard navigation: Make sure users can navigate through the website using only the keyboard, and that the focus order makes sense. This includes making sure interactive elements are focusable and that the focus is visible.

Use appropriate heading levels: Implement proper content hierarchy using appropriate heading levels (h1, h2, h3, etc.). Start with an

tag for the main heading of the page and use subsequent headings like

,

for subheadings.

Improve semantic HTML structure: Utilize semantic HTML elements like

, , , , , and to provide a better understanding of the content structure for screen readers.

Positive testing:

Check if appropriate aria-* attributes are present on interactive elements (e.g., navigation menu).

Verify that keyboard navigation is possible and follows a logical focus order.

Ensure that appropriate heading levels are used (e.g.,

for the main heading,

for subheadings, etc.).

Confirm that semantic HTML elements like

, , , , , and are used correctly.

For later!

Positive tests for making a website accessible include testing that the website meets technical standards such as WCAG 2.1 Level AA, verifying that the website is designed inclusively and does not discriminate against individuals with disabilities, testing that the website design is accessible, and verifying that the business has an accessibility policy in place that is prominently displayed, regularly reviewed, and updated as needed to reflect changes in laws and standards.

Negative tests:

Check if any interactive elements are missing aria-* attributes, making them less accessible for assistive technologies.

Verify if any elements are not reachable via keyboard navigation, which could hinder the user experience for keyboard-only users.

Check if the heading levels are skipped or incorrectly used (e.g., jumping from

to

without an

in between).

Confirm that non-semantic HTML elements are used instead of appropriate semantic ones (e.g., using a

instead of a or ).

For later!

Negative tests for making a website accessible include testing that the website does not meet technical standards, verifying that the website design is exclusive and discriminatory against individuals with disabilities, testing that the website design is not accessible, and verifying that the business does not have an accessibility policy in place or that the policy is not regularly reviewed and updated to reflect changes in laws and standards. These negative tests can help businesses identify areas of non-compliance and take corrective measures.

Testing Requirements for Accessibility:

Some basic tools and technologies that can be useful for ensuring website accessibility on a basic webpage include:

  • Alternate text for images: test that if images are not loading, there is enough description to be able to picture what is supposed to be there.

  • Label element for newsletter input: Used a label element to associate the form input with its purpose

Later testing

  • Accessibility testing tools, such as Lighthouse in Google Chrome's DevTools to identify and fix accessibility issues on the website.

  • Accessible design and development frameworks, such as Bootstrap to provide pre-built components and patterns for accessible website design.

  • Documentation and policy templates, to help businesses create and maintain accessibility policies and documentation.

⚠️ **GitHub.com Fallback** ⚠️