The document discusses why digital accessibility is important and why people should care about it. Some key points include: - Digital accessibility is about making websites, apps, and documents accessible to everyone by removing barriers. - It's required by law and regulations to ensure accessibility for people with disabilities. - Ensuring accessibility saves costs and provides competitive advantages for organizations. - As the number of people with disabilities increases, accessibility will become more important. - Accessibility benefits everyone as we will all experience disabilities at some point in our lives.

1. Why should we care about
Digital Accessibility?
(and join the Digital Accessibility CoP)?
https://matthewdeeprose.github.io/whycare.html

2. What is 1
Digital accessibility is the process of
making websites, mobile apps and
documents accessible to everyone.
https://matthewdeeprose.github.io/whycare.html

3. What is 2
Digital accessibility is the process of
making websites, mobile apps and
documents accessible to everyone.
https://matthewdeeprose.github.io/whycare.html

4. What is 3
Digital accessibility is the process of
making websites, mobile apps and
documents accessible to everyone.
https://matthewdeeprose.github.io/whycare.html

5. Why should we care? (5) Competitive advantage
Maximise the
potential of the
University’s digital
estate for all
stakeholders by
removing barriers.
It’s the law. It saves
money.
It’s the right
thing to do.
Competitive
advantage.
https://matthewdeeprose.github.io/whycare.html

6. Maximise the potential of the University’s digital estate
for all stakeholders by removing barriers.
https://matthewdeeprose.github.io/whycare.html

7. Students 1
The proportion of new students
disclosing a disability increased by 41%
this academic year*.
* https://go.soton.ac.uk/dkr https://matthewdeeprose.github.io/whycare.html

8. Students 2
The proportion of new students
disclosing a disability increased by 41%
this academic year*.
* https://go.soton.ac.uk/dkr https://matthewdeeprose.github.io/whycare.html

9. Students 3
Students who study at UoS with a
disclosed disability are less likely to
continue their programme of study.
http://www.southampton.ac.uk/assets/sharepoint/groupsite/Administration/SitePublisher-document-
store/Documents/University%20of%20Southampton%20Access%20and%20Participation%20Plan%2020
20-21%20-%202024-25.pdf
https://matthewdeeprose.github.io/whycare.html

10. Students 4
Students who study at UoS with a
disclosed disability are less likely to
continue their programme of study.
http://www.southampton.ac.uk/assets/sharepoint/groupsite/Administration/SitePublisher-document-
store/Documents/University%20of%20Southampton%20Access%20and%20Participation%20Plan%2020
20-21%20-%202024-25.pdf
https://matthewdeeprose.github.io/whycare.html

11. Maximise the potential of the University’s digital estate
for all stakeholders.
Microsoft Design
https://matthewdeeprose.github.io/whycare.html

12. Increasing need for assistive technology
https://matthewdeeprose.github.io/whycare.html

13. What does the strategy say?
“[enable] the exploitation of
digital technology by the
University”
… for all!
https://matthewdeeprose.github.io/whycare.html

14. Do we know how accessible our services are? 3
• Can all of our services be used
with a keyboard?
• Can all of our services be used
at 400% zoom without
horizontal scrolling?
• Do our services have text and
UI components with enough
contrast?
https://matthewdeeprose.github.io/whycare.html

15. Do we know how accessible our services are? 2
• Can all of our services by used
with a keyboard?
• Can all of our services be used
at 400% zoom without
horizontal scrolling?
• Do our services have text and
UI components with enough
contrast?
https://matthewdeeprose.github.io/whycare.html

16. Do we know how accessible our services are? 1
• Can all of our services by used
with a keyboard?
• Can all of our services be used
at 400% zoom without
horizontal scrolling?
• Do our services have text and
UI components with enough
contrast?
https://matthewdeeprose.github.io/whycare.html

17. It’s the law. 1
https://matthewdeeprose.github.io/whycare.html

18. It’s the law. 2
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile Applications)
No. 2 Accessibility Regulations 2018
Equality Act 2010
Does not apply in Northern
Ireland
Disability Discrimination Act 1995
Applies to all UK
Standard - EN 301 549
Accessibility requirements suitable for public procurement of
ICT products and services in Europe
REGULATION (EU) No 1025/2012 OF THE EUROPEAN
PARLIAMENT AND OF THE COUNCIL
WCAG 2.X Level AA
The “failure to make a reasonable adjustment” definition in the 2018 SI refers to the detail
already determined in the above two acts.
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
https://matthewdeeprose.github.io/whycare.html

19. Accessibility Statement
https://matthewdeeprose.github.io/whycare.html

20. Accessibility Statement (1)
1. What is not accessible, and why.
2. Accessible alternatives.
3. Contact process.
4. Enforcement procedure.
https://matthewdeeprose.github.io/whycare.html

21. Accessibility Statement (2)
1. What is not accessible, and why.
2. Accessible alternatives.
3. Contact process.
4. Enforcement procedure.
https://matthewdeeprose.github.io/whycare.html

22. Accessibility Statement (3)
1. What is not accessible, and why.
2. Accessible alternatives.
3. Contact process.
4. Enforcement procedure.
https://matthewdeeprose.github.io/whycare.html

23. Accessibility Statement (4)
1. What is not accessible, and why.
2. Accessible alternatives.
3. Contact process.
4. Enforcement procedure.
https://matthewdeeprose.github.io/whycare.html

24. The Public Sector Bodies (Websites and Mobile
Applications) (No. 2) Accessibility Regulations 2018
timeline
23 September
2019
Websites published
on or after 23
September 2018.
Office file formats*
Extranets and
intranets**
23 September
2020
Websites published
before 22 September
2018.
23 June 2021
Mobile apps.
*Office file formats published from 23 September 2018, and any published before 23rd September 2018 which are needed for active administrative processes relating to the
tasks performed by the public sector body.
**Content of extranets and intranets published on or after 23rd September 2019, and any content published before 23rd September 2019 that has been substantially
revised. https://matthewdeeprose.github.io/whycare.html

25. It saves money.
https://matthewdeeprose.github.io/whycare.html

26. It saves money 2
Following
accessible
practices
reduces
page size
and load
time.*
Accessible mark up
requires less
maintenance to
make compatible
with future
devices.**
Standardising with
accessible user
interface patterns
and components
means not
reinventing the
wheel.
Students who
study at UoS
with a disclosed
disability are
less likely to
continue their
programme of
study***
* https://www.mightybytes.com/blog/digital-accessibility-series-part-one/
** https://www.w3.org/WAI/fundamentals/accessibility-principles/#robust
*** UoS Access and Participation Plan https://matthewdeeprose.github.io/whycare.html

27. It’s the right thing to do.
https://matthewdeeprose.github.io/whycare.html

28. It’s the right thing to do 3
Accessibility features in
products and services
often solve
unanticipated
problems. *
40% of households
have at least 1 disabled
person. **
We all will benefit from
Assistive Technologies
at some point in our
lives. ***
* https://www.w3.org/WAI/business-case/
** https://www.scope.org.uk/media/disability-facts-figures/
*** https://www.who.int/news-room/fact-sheets/detail/assistive-technology
https://matthewdeeprose.github.io/whycare.html

29. It’s the right thing to do 2
https://matthewdeeprose.github.io/whycare.html

30. What does the strategy say? (2)
“We will:
• Get the basics right
• Continually [improve] our
services”
https://matthewdeeprose.github.io/whycare.html

31. Competitive advantage.
https://matthewdeeprose.github.io/whycare.html

32. Your competitive advantage
Many roles in iSolutions
already have accessibility
within their job description or
person specification.
(6 roles, 49 current posts)
https://matthewdeeprose.github.io/whycare.html

33. Software Engineer
“Knowledge of modern HTML and
CSS and the impact that high quality
mark-up can have on performance,
accessibility and discoverability.”
Person Specification – Essential
https://matthewdeeprose.github.io/whycare.html

34. Senior Software Engineer / Senior Software Engineer
Team Lead
“Experience of modern HTML and
CSS and the impact that high quality
mark-up can have on performance,
accessibility and discoverability.”
Person Specification – Essential
https://matthewdeeprose.github.io/whycare.html

35. Team Manager – Digital Learning
“Contribute, and encourage others to
contribute, to communities of best practice
(e.g. training, accessibility, user
experience) in the development of policies
and procedures which aim to showcase
best practice across different delivery
streams.”
Key accountabilities
https://matthewdeeprose.github.io/whycare.html

36. Multimedia Development Team Lead / Multimedia
Developer
“Knowledge of accessibility issues
relating to multimedia design.”
Person Specification - Desirable
https://matthewdeeprose.github.io/whycare.html

37. Expertise in digital accessibility will be required by
companies who do business around the world.
https://matthewdeeprose.github.io/whycare.html

38. Expertise in digital accessibility will be required by
companies who do business around the world. (1)
Country Name
Australia World Wide Web Access: Disability Discrimination Act
Brazil e-MAG, Modelo de Acessibilidade de Governo Eletrônico
Canada Standard on Web Accessibility
Israel Israeli standard 5568
Italy Stanca Act
Japan Japanese Industrial Standards X 8341-3
Norway
Forskrift om universell utforming av informasjons- og kommunikasjonsteknologiske
(IKT)-løsninger
https://en.wikipedia.org/wiki/Web_accessibility#Web_accessibility_legislation
https://www.lflegal.com/2013/05/gaad-legal/
https://matthewdeeprose.github.io/whycare.html

39. European Accessibility Act
Covers products and services
that have been identified as
being most important for
persons with disabilities while
being most likely to have
diverging accessibility
requirements across EU
countries.
• Computers and operating systems
• ATMs, ticketing and check-in
machines
• Smartphones
• TV equipment related to digital
television services
• Telephony services and related
equipment
• Access to audio-visual media
services such as television broadcast
and related consumer equipment
• Services related to air, bus, rail and
waterborne passenger transport
• Banking services
• e-books
• e-commerce
Directive (EU)
2019/882
European Accessibility Act
https://matthewdeeprose.github.io/whycare.html

40. An edge in the job market?
Less than 3 % of University tech
programmes include accessibility.
*
63% of tech companies cannot
staff accessibility needs. **
93% say demand for accessibility
skills will increase in the future **
* Teach Access Institutions course list (coded), 2018
** Accessible Technology Skills Gap Report, PEAT, 2018.
https://matthewdeeprose.github.io/whycare.html

41. What did SLT say? (3)
“…We are going to deliver
amazing accessibility.
Because it is the right
thing to do”
Accessibility Situation Report:
An intro and update.
• Dave Key
• 18 December 2020
• iSolutions All-staff meeting.
https://matthewdeeprose.github.io/whycare.html

42. Accessibility is a journey
https://matthewdeeprose.github.io/whycare.html

43. Digital Accessibility Community of Practice
• Join our Digital Accessibility
Community of Practice team
using this join code ryprgyd
• This guide explains how to
join a team using a code.
https://matthewdeeprose.github.io/whycare.html

44. Towards
amazing accessibility!
Introduction to accessibility testing and “shifting left” to operationalise amazing
accessibility throughout the development life cycle.
https://matthewdeeprose.github.io/whycare.html

45. Current state
Current state
Baseline accessibility /
Legal compliance
Amazing accessibility
20 May 15:00 – 16:00!
https://matthewdeeprose.github.io/whycare.html

46. https://matthewdeeprose.github.io/whycare.html