Please enable JavaScript.
Coggle requires JavaScript to display documents.
EQUALITY ACT 2010 - Coggle Diagram
EQUALITY ACT 2010
the equality act 2010 overview
It replaced the disability discrimination act, along with 115 other pieces of legislation, including the sex discrimination act, equal pay act and race relations act.
The act ensure all website owners oblige by this law and ensure that there website is accessible to everyone not just a certain group of people.
They way website owners ensure that they are obliging by this law is that they ensure that their websites have adopted a design that has certain colour and layouts that makes sure everyone is able to understand and use the website.
A key piece of UK legislation that aims to protect to protect individuals from discrimination and promote equality across various sectors- including the digital and technology sectors.
The equality act 2010 have several characteristics that are especially relevant when discussing IT accessibility:
-Disability
-Age
-Gender reassignment, race, religion
Many IT areas are affected by the act like WEBSITES AND WEB APPLICATIONS
MOBILE APPLICATIONS
DIGITAL SERVICES
SOFTWARE TOOLS AND INTRANETS
open accessibility framework
The open accessibility framework is a guideline used to help make digital systems, websites, apps and interfaces accessible to everyone-especially people with disabilities
It main goal is to make sure that technology is designed so everyone can use it, regardless of their physical or cognitive abilities
WHY IS OAF IMPORTANT: around 1 in 5 people have a disability that affects how they use computers and the web. Without accessibility features, many users can't access content, services, or education online.
The OAF helps developers, designers, and IT terms create tech that includes everyone
The OAF is built around 5 key areas
User needs:
-Focus on the specific needs of users with different disabilities
Examples: People who are blind, deaf, have mobility problems, or learning difficulties
-Systems should adapt to the needs.
Examples: A website might need to support screen readers or allow keyboard navigation
Assistive Technologies:
-These are tools that help people with disabilities use computers
Examples: screen readers, voice recognition, braille displays, eye tracking systems.
-The OAF supports integration with these tools.
Examples: A visually impaired user might use a screen reader to hear website content.
Accessibility APIs:
-APIs allows apps and software to "communicate" with assistive tech.
-The OAF encourages developers to use these APIs so assistive tools can understand the software
Examples: If a button says "submit", the API ensures the screen reader reads that aloud properly
Application support:
-Apps and websites must follow good accessibility design practices
This includes:
-Proper colour contrast
-Clear navigation
-Text alternative for images
-Captions for videos
-Responsive layout for different devices
Platforms services:
-These are built-in services in operating systems that support accessibility
-They help make sure apps behave in ways that assistive tech can understand
WEB CONTENT ACCESSABILITY GUIDELINES
It is a set of rules and best practices that help make websites and digital content accessible to everyone- including people with disabilities like visual, hearing, mobility, or learning difficulties.
These guidelines are created by the W3C and are used worldwide
The main goal: To help web designers and developers make websites that are:
-easy to use
-understandable
-accessible to everyone
Especially users who:
-Are blind or visually impaired
-Are deaf or hard of hearing
-Have mobility issues
-Have cognitive or learning difficulties
-Use assistive technologies
P- perceivable O-operable
U-understandable R-Robust
P- users must be able to see, hear or sense the content
O- users must be able to use the website
U- content must be easy to read and follow
R- content must work well with different devices and assistive tech