With the rapid move to online teaching, ensuring equitable access to our learning environment has never been more important. Recent legislation has brought an accessibility requirement for public sector organisations such as Universities. How can we ensure that our Blackboard environment reflects our institutional brand whilst following accessibility guidelines?
Customising the Blackboard Responsive theme for the Learn Original Experience continues to be a hot topic on the Blackboard Community site. We customise the theme both to improve the user experience, and to brand our environment with our institutional colours.
In this session I will put recent legislative and regulatory changes that relate to accessibility into a global context and explain how they impact University platforms such as Blackboard.
Using examples and developments from my own experience at the University of Southampton, I will provide practical advice and tips on what we should be doing when we customise our Blackboard theme. We all want our Blackboard environments to look great and appear congruent when viewed alongside our other institutional platforms. We also want to ensure changes we make are inclusive to our whole user community.
I will demonstrate how you may check the accessibility of your own custom Blackboard theme and illustrate the application of a number of the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines to Blackboard theme customisation. I will also discuss how the work we do in this area can inform the accessibility statements we are required to create for our Virtual Learning Environment.
2. https://matthewdeeprose.github.io/bluffer2020.html
Agenda
Topic Why you should care
Ensuring equitable access to our learning
environment has never been more important.
The accessibility of our VLE matters even more when
our staff and students are relying on it for online
delivery.
Reflections on last year’s talk. This presentation builds on theme customisation, this
time with a focus on accessibility.
How the various web accessibility rules and
regulations are related.
I believe it is important to know how the recent EU
web accessibility regulations relate to the wider
standards of the W3C, and what changes we should
expect going forward.
Blackboard Theme accessibility considerations: Use
of Colour, Colour Contrast, Focus Indicators,
Movement, and Usability.
Practical examples of the application of the
regulations and standards within the context of Bb
theme customisation.
4. https://matthewdeeprose.github.io/bluffer2020.html
Assumed:
• That you have watched or will watch last
year’s “Bluffers guide to customising the
Blackboard theme”.
• That you have administrator access to your
environment or know someone who does.
• That you will test anything before
implementing in live.
Not assumed :
• That you have expertise in CSS.
• That you are an expert in accessibility.
• That you will watch the whole presentation.
Assumptions
5. https://matthewdeeprose.github.io/bluffer2020.html
• This presentation has:
• More content.
• Latest updates including new details about
WCAG 2.2
• More time.
• More code examples.
If you saw my talk at the MoCo session at this year’s Durham conference
.mainButton a:focus,
.secondaryButton a:focus,
div#puller a:focus,
.item a:focus,
.student-preview-control a:focus,
.attachments a:focus,
.breadcrumbs a:focus {
outline: 3px solid #00131D !important;
outline-offset: 3px !important;
transition: outline-offset .2s linear !important; }
9. https://matthewdeeprose.github.io/bluffer2020.html
About me
• Managing the Blackboard service at the University of
Southampton since July 2000.
• Blackboard MVP.
• Previous TLC presentations:
– Upgrade Club (2018).
– Bluffer’s guide to customising the 2016 Blackboard
theme. (2019).
• Presentations at this year’s TLC:
– The Bluffer’s Guide to Blackboard Theme Accessibility.
– Better Blackboard Help.
@vleguru
26. https://matthewdeeprose.github.io/bluffer2020.html
Reflections on last year’s talk
• Video now on YouTube, thanks again to Nathan
Cobb for organising the recording.
• The revised video is a multi-media ‘experience’
including almost 20 minutes of bonus materials
and is subtitled.
• Unfortunately most of the links I referenced are
no longer available following the migration to
the new Blackboard community site.
28. https://matthewdeeprose.github.io/bluffer2020.html
Reflections on last year’s talk
• Continuing on my journey, here are some
online resources that have helped me a lot that
I recommend you check out:
– https://developer.mozilla.org/en-
US/docs/Learn
– https://css-tricks.com/
– https://www.a11ywithlindsey.com/
– https://groups.google.com/a/d.umn.edu/foru
m/?hl=en#!forum/webdev
29. https://matthewdeeprose.github.io/bluffer2020.html
Reflections on last year’s talk
• There are now about 1700 lines of customised
CSS in our theme.
• Take a tour of the work I have been doing on
our Blackboard environment in my blog post
“Let me show you my Blackboard” on the
community site:
– https://community.blackboard.com/blogs/14/85
33. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
34. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
Real Decreto 1112/2018, de 7 de septiembre, sobre
accesibilidad de los sitios web y aplicaciones para
dispositivos móviles del sector público.
Gesetz zur Umsetzung der Richtlinie (EU) 2016/2102
des Europäischen Parlaments und des Rates vom 26.
Oktober 2016 über den barrierefreien Zugang zu den
Websites und mobilen Anwendungen öffentlicher
Stellen
Besluit van 3 mei 2018, houdende tijdelijke regels
betreffende de toegankelijkheid van de websites en
mobiele applicaties van overheidsinstanties (Tijdelijk
besluit digitale toegankelijkheid overheid)
Loi du 19 juillet 2018 relative à l'accessibilité des sites
internet et des applications mobiles des organismes du
secteur public
List of national transposition
measures:
https://eur-lex.europa.eu/legal-
content/en/NIM/?uri=CELEX:32016L2102
+23
more
35. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
Disability
Discrimination Act 1995
Applies to all UK
The “failure to make a reasonable adjustment” definition in the 2018 SI
refers to the detail already determined in the above two acts.
Equality Act 2010
Does not apply in Northern
Ireland
36. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
Disability
Discrimination Act 1995
Applies to all UK
The “failure to make a reasonable adjustment” definition in the 2018 SI
refers to the detail already determined in the above two acts.
Equality Act 2010
Does not apply in Northern
Ireland
COM(2010)636
European Disability Strategy 2010-2020:
A Renewed Commitment to a Barrier-
Free Europe
COM(2010)245
A Digital Agenda for
Europe
37. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
Disability
Discrimination Act 1995
Applies to all UK
The “failure to make a reasonable adjustment” definition in the 2018 SI
refers to the detail already determined in the above two acts.
Equality Act 2010
Does not apply in Northern
Ireland
Convention on the Rights of Persons
with Disabilities (CRPD) 2006
COM(2010)636
European Disability Strategy 2010-2020:
A Renewed Commitment to a Barrier-
Free Europe
COM(2010)245
A Digital Agenda for
Europe
38. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
Disability
Discrimination Act 1995
Applies to all UK
The “failure to make a reasonable adjustment” definition in the 2018 SI
refers to the detail already determined in the above two acts.
Equality Act 2010
Does not apply in Northern
Ireland
Convention on the Rights of Persons
with Disabilities (CRPD) 2006
COM(2010)636
European Disability Strategy 2010-2020:
A Renewed Commitment to a Barrier-
Free Europe
COM(2010)245
A Digital Agenda for
Europe
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
39. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
Disability
Discrimination Act 1995
Applies to all UK
The “failure to make a reasonable adjustment” definition in the 2018 SI
refers to the detail already determined in the above two acts.
Equality Act 2010
Does not apply in Northern
Ireland
Convention on the Rights of Persons
with Disabilities (CRPD) 2006
COM(2010)636
European Disability Strategy 2010-2020:
A Renewed Commitment to a Barrier-
Free Europe
COM(2010)245
A Digital Agenda for
Europe
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
40. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
Disability
Discrimination Act 1995
Applies to all UK
The “failure to make a reasonable adjustment” definition in the 2018 SI
refers to the detail already determined in the above two acts.
Equality Act 2010
Does not apply in Northern
Ireland
Convention on the Rights of Persons
with Disabilities (CRPD) 2006
COM(2010)636
European Disability Strategy 2010-2020:
A Renewed Commitment to a Barrier-
Free Europe
COM(2010)245
A Digital Agenda for
Europe
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
ISO/IEC
40500:2012
41. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
Disability
Discrimination Act 1995
Applies to all UK
The “failure to make a reasonable adjustment” definition in the 2018 SI
refers to the detail already determined in the above two acts.
Equality Act 2010
Does not apply in Northern
Ireland
Convention on the Rights of Persons
with Disabilities (CRPD) 2006
COM(2010)636
European Disability Strategy 2010-2020:
A Renewed Commitment to a Barrier-
Free Europe
COM(2010)245
A Digital Agenda for
Europe
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
Section 508 of the
Rehabilitation Act of 1973
ISO/IEC
40500:2012
42. https://matthewdeeprose.github.io/bluffer2020.html
How the various rules and regulations are related.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
Directive (EU) 2016/2102
On the Accessibility of the websites and mobile
applications of public sector bodies
Disability
Discrimination Act 1995
Applies to all UK
The “failure to make a reasonable adjustment” definition in the 2018 SI
refers to the detail already determined in the above two acts.
Equality Act 2010
Does not apply in Northern
Ireland
Convention on the Rights of Persons
with Disabilities (CRPD) 2006
COM(2010)636
European Disability Strategy 2010-2020:
A Renewed Commitment to a Barrier-
Free Europe
COM(2010)245
A Digital Agenda for
Europe
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
Section 508 of the
Rehabilitation Act of 1973
Americans with
Disabilities Act (ADA)
Standards for Accessible
Design in September 2010
ISO/IEC
40500:2012
43. https://matthewdeeprose.github.io/bluffer2020.html
Global Momentum
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
44. https://matthewdeeprose.github.io/bluffer2020.html
Global Momentum
Directive (EU) 2016 / 2102
On the Accessibility of the websites and
mobile applications of public sector bodies
Entered into force on June 27, 2019 and
has to be implemented in national regulation
on June 28, 2022 at the latest.
Takes effect from 28 June 2025.
Directive (EU) 2019/882
European Accessibility Act
46. https://matthewdeeprose.github.io/bluffer2020.html
Global Momentum
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.
Directive (EU) 2019/882
European Accessibility Act
• 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
47. https://matthewdeeprose.github.io/bluffer2020.html
Continual Developments
View EN 301 549 at
http://mandate376.standards.eu/standard
Chapters 9, 10, and 11 are
relevant to the regulations.
Directive (EU) 2016 / 2102
On the Accessibility of the websites and
mobile applications of public sector bodies
Standard - EN 301 549
Accessibility requirements suitable for
public procurement of ICT products and
services in Europe
48. https://matthewdeeprose.github.io/bluffer2020.html
Continual Developments
Updated:
• August 2018
• November 2019
• Now uses WCAG 2.1 AA (previously
WCAG 2.0 AA.)
See https://www.etsi.org/
Directive (EU) 2016 / 2102
On the Accessibility of the websites and
mobile applications of public sector bodies
Standard - EN 301 549
Accessibility requirements suitable for
public procurement of ICT products and
services in Europe
50. https://matthewdeeprose.github.io/bluffer2020.html
The new European Standard on 'Accessibility requirements suitable for public procurement of ICT products and services in Europe' (EN 301 549) was
produced by CEN, CENELEC and ETSI in response to a request from the European Commission (Mandate 376). It was developed by an international team of
experts, with the participation of the ICT industry and organizations representing consumers, people with disabilities and older persons.
The new European Standard is complemented by a series of three Technical Reports (TR 101 550, TR 101 551 and TR 101 552). Together, these documents
set out accessibility requirements that can be applied to a wide range of products and services related to ICT, including computers, smartphones and other
digital devices, ticketing machines, websites and emails. The aim is to ensure that ICT products and services are accessible either directly or through
compatibility with assistive technologies such as text-to-speech, so that everyone can access information and use services that are being delivered
electronically.
The new European Standard and its accompanying Technical Reports provide a framework for developing a wide range of applications that will make ICT
products and services more accessible for the 80 million Europeans who are living with various types of disability. Potential applications include audio and/or
tactile interfaces that can be used by visually impaired persons, or hardware such as smartphones and laptops that can be operated using one hand.
EN 301 549 is the most up-to-date standard for ICT accessibility, and it was developed through an inclusive process with the active involvement of relevant
stakeholders. While the accessibility requirements are defined in a form that is suitable for use in public procurement, they could also be used in other
contexts such as procurement in the private sector.
Find this and other information here: https://www.cencenelec.eu/News/Press_Releases/Pages/PR-2014-03.aspx
For further clarification contact:
- https://www.cencenelec.eu/helpers/Pages/ContactUs.aspx
- http://mandate376.standards.eu/contact
54. https://matthewdeeprose.github.io/bluffer2020.html
Global Momentum
WCAG 2.1
WCAG 2.2 will be released in November 2020
First Public Working Draft published on 27 February 2020
https://www.w3.org/TR/WCAG22/
WCAG 2.2
Project AG for the next generation of WCAG is expected to
have new standards in November 2022 and is currently
being worked on by “Taskforce Silver”.
55. https://matthewdeeprose.github.io/bluffer2020.html
Understand how the
regulations will impact your
institution.
Make a plan to fix any issues
you find.
Check the accessibility of your
websites.
Publish an accessibility
statement.
Four steps to ensure compliance with the Accessibility Regulations
https://www.gov.uk/government/publications/online-accessibility-regulations-campaign-supporter-pack/gds-accessibility-regulations-campaign-information-for-
education
Bb community: “Show us your
Accessibility Statement”
https://bit.ly/2zpXQ84
56. https://matthewdeeprose.github.io/bluffer2020.html
Out of scope In scope When
Websites published on or after 23 September 2018. After 22nd September 2019.
Websites published before 22 September 2018. After 22nd September 2020.
Mobile apps. After 22nd June 2021.
Office file formats published before 23rd September
2018, unless such content is needed for active
administrative processes relating to the tasks performed
by the public sector body.
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.
After 22nd September 2019.
Pre-recorded time-based media published before 23rd
September 2020.
Pre-recorded time-based media published on or after 23rd
September 2020.
After 23rd September 2020.
Live time-based media.
Recordings of live time-based media that are used on or after 23rd
September 2020.
After 23rd September 2020.
Content of extranets and intranets published before
23rd September 2019, or until such time as the website
undergoes a substantial revision, whichever is sooner.
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.
From 23rd September 2019.
Content of websites and mobile applications qualifying
as archives, except those that are needed for active
administrative processes or have been updated or
edited since 23 September 2019.
Content of websites and mobile applications qualifying as archives
that are needed for active administrative processes or have been
updated or edited since 23 September 2019.
After 22nd September 2020.
Maps. An accessible alternative to maps should be provided.
Depends on publishing date of
host website (see above).
Reproductions of items in heritage collections that
cannot be made fully accessible.
Some accessibility requirements for websites or mobile applications
should still be complied with as regards the metadata linked to the
reproduction of items in heritage collections.
Depends on publishing date of
host website (see above).
57. https://matthewdeeprose.github.io/bluffer2020.html
Out of scope In scope When
Mobile apps. After 22nd June 2021.
Office file formats published before 23rd
September 2018, unless such content is needed
for active administrative processes relating to
the tasks performed by the public sector body.
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.
After 22nd September
2019.
Pre-recorded time-based media published
before 23rd September 2020.
Pre-recorded time-based media published on or after 23rd
September 2020.
After 23rd September
2020.
Live time-based media.
Recordings of live time-based media that are used on or
after 23rd September 2020.
After 23rd September
2020.
Content of extranets and intranets published
before 23rd September 2019, or until such time
as the website undergoes a substantial revision,
whichever is sooner.
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.
From 23rd September
2019.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
58. https://matthewdeeprose.github.io/bluffer2020.html
Out of scope In scope When
Content of extranets and intranets
published before 23rd September
2019, or until such time as the website
undergoes a substantial revision,
whichever is sooner.
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.
From 23rd
September 2019.
Statutory Instrument 2018 No. 952
The Public Sector Bodies (Websites and Mobile
Applications) No. 2 Accessibility Regulations 2018
60. https://matthewdeeprose.github.io/bluffer2020.html
From the Government Digital
Service (UK)
“Most higher and further education
providers are considered to be in scope
for the regulations, due to their
dependence on government funding.
However, funding arrangements in this
sector differ, therefore organisations
should seek legal advice if they are
unsure of their position.”
https://www.gov.uk/government/publications/online-accessibility-regulations-campaign-supporter-pack/gds-
accessibility-regulations-campaign-information-for-education
61. https://matthewdeeprose.github.io/bluffer2020.html
“The question of how to prioritise actions
and what constitutes a ‘disproportionate
burden’ is a very real one for institutions.
GDS advise institutions to seek their own
legal advice on this - there is therefore a
prospect of multiple institutions spending
money on the same (or even contradictory)
legal advice.”
https://www.ucisa.ac.uk/-/media/Files/UCISA/Publication-files/Directors-cut/Digital-accessibility-directors-cut.pdf
62. https://matthewdeeprose.github.io/bluffer2020.html
ADA / Dominos
Domino's Pizza v. Guillermo Robles
9th Circuit Court of Appeals, in San Francisco,
ruled that the Dominos app and website should
be accessible.
• Dominos appealed to the Supreme Court, who
formally declined to hear the case.
"Here's what's shocking about
Domino's: like Target [in 2008], just
fixing the problem costs a great deal
less than suing.
Whitney Quesenbery, Center for Civic Design.
https://arstechnica.com/tech-policy/2019/10/accessibility-the-future-and-why-dominos-matters/
So they were suing
for the right to
discriminate…"
64. https://matthewdeeprose.github.io/bluffer2020.html
“A website is not usable unless it is
accessible.”
Krug, S., 2006. Don’t make me think:
a common sense approach to
web usability. (New Riders Press.)
“We will benefit from accessible
features and design at different
points in our lives.”
The Business Case for Digital
Accessibility:
https://www.w3.org/WAI/business-
case/
Accessibility / Usability / Inclusivity
66. https://matthewdeeprose.github.io/bluffer2020.html
When we introduced the 2016
responsive theme in 2019 we
wanted the interface to be both:
Making the Blackboard responsive theme on brand and accessible
✔ “On brand” (using the
institutional colour
palette).
✔ Compliant with the new
web accessibility
regulations.
72. https://matthewdeeprose.github.io/bluffer2020.html
More than two million
people in the UK live
with a visual
impairment.*
Many more report
having difficulties with
their sight.*
4.5% of the British
population are colour
blind.**
• Red–green colour blindness
affects up to 8% of males
and 0.5% of females of
Northern European
descent.***
• The ability to see colour also
decreases in old age.***
Example 1: Colour contrast in context
* https://abilitynet.org.uk/blog/visual-impairment-and-computing-common-questions
** http://www.colourblindawareness.org/colour-blindness/
*** https://en.wikipedia.org/wiki/Color_blindness
75. https://matthewdeeprose.github.io/bluffer2020.html
Level A
Colour is not used as the only visual
means of conveying information…
WCAG 1.4.1 Use of Colour
9.2.10 Use of colour
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.4.1 Use of
Colour
Standard - EN 301 549
Accessibility requirements suitable for
public procurement of ICT products
and services in Europe
http://mandate376.standards.eu/
✔
X
76. https://matthewdeeprose.github.io/bluffer2020.html
Level AA
The visual presentation of the
following have a contrast ratio of at
least 3:1 against adjacent colour(s):
• Graphical Objects
• User Interface Components
WCAG 1.4.11 Non-text Contrast
9.1.4.11 Non-text contrast
Where ICT is a web page, it shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-
text Contrast.
ETSI EN 301 549 V3.1.1
(2019-11)
Accessibility requirements suitable for
public procurement of ICT products
and services in Europe
https://www.etsi.org/
77. https://matthewdeeprose.github.io/bluffer2020.html
Level AA
The visual presentation of the
following have a contrast ratio of at
least 3:1 against adjacent colour(s):
• Graphical Objects
“Parts of graphics required to
understand the content, except
when a particular presentation of
graphics is essential to the
information being conveyed.”
WCAG 1.4.11 Non-text Contrast
78. https://matthewdeeprose.github.io/bluffer2020.html
Level AA
The visual presentation of the
following have a contrast ratio of at
least 3:1 against adjacent colour(s):
• User Interface Components
“Visual information required to
identify user interface components
and states, except for inactive
components or where the
appearance of the component is
determined by the user agent and
not modified by the author”.
WCAG 1.4.11 Non-text Contrast
81. https://matthewdeeprose.github.io/bluffer2020.html
1.4.1 Non-text Contrast in Blackboard theme
Ratio: 7.33:1 ✔
/* Change primary menu button colour -
(+ Icon) */
.mainButton > a {
background: #005c84;
}
/* Change secondary menu button
colours (Reorder, Refresh, Course Files
buttons) */
.secondaryButton > a,
.mainButton h2 > a,
.secondaryButton h2 > a {
background: #005c84;
}
82. https://matthewdeeprose.github.io/bluffer2020.html
Large Text
Large-scale text and images of large-
scale text have a contrast ratio of at
least 3:1;
http://mandate376.standards.eu/
Level AA
The visual presentation of text and
images of text has a contrast ratio of
at least 4.5:1 except for the
following:
WCAG 1.4.3 Contrast (Minimum)
Standard - EN 301 549
Accessibility requirements suitable for
public procurement of ICT products
and services in Europe
9.2.12 Contrast (minimum)
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.4.3
Contrast (Minimum).
83. https://matthewdeeprose.github.io/bluffer2020.html
Level AA
The visual presentation of text and
images of text has a contrast ratio of
at least 4.5:1 except for the
following:
WCAG 1.4.3 Contrast (Minimum)
Standard - EN 301 549
Accessibility requirements suitable for
public procurement of ICT products
and services in Europe
http://mandate376.standards.eu/
Incidental
Text or images of text that
• are part of an inactive user
interface component,
• are pure decoration,
• are not visible to anyone,
• that are part of a picture that
contains significant other visual
content.
84. https://matthewdeeprose.github.io/bluffer2020.html
Logotypes
Text that is part of a logo or brand
name has no contrast requirement.
Level AA
The visual presentation of text and
images of text has a contrast ratio of
at least 4.5:1 except for the
following:
WCAG 1.4.3 Contrast (Minimum)
Standard - EN 301 549
Accessibility requirements suitable for
public procurement of ICT products
and services in Europe
http://mandate376.standards.eu/
9.2.12 Contrast (minimum)
Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 1.4.3
Contrast (Minimum).
http://mandate376.standards.eu/
86. https://matthewdeeprose.github.io/bluffer2020.html
Visual presentation of text and images of text…
Ratio: 2.49:1 X
Level AA
The visual presentation of text and
images of text has a contrast ratio of
at least 4.5:1
Level AAA
The visual presentation of text and
images of text has a contrast ratio of
at least 7:1.
87. https://matthewdeeprose.github.io/bluffer2020.html
Visual presentation of text and images of text…
Ratio: 14.44:1 ✔
Level AA
The visual presentation of text and
images of text has a contrast ratio of
at least 4.5:1
Level AAA
The visual presentation of text and
images of text has a contrast ratio of
at least 7:1.
88. https://matthewdeeprose.github.io/bluffer2020.html
Visual presentation of text and images of text…
Ratio: 14.44:1 ✔
.actionBar .mainButton h2 > a {
color: #FFFFFF !important;
background: none scroll 0 0 #002E3B
!important;
text-shadow: none !important;
text-decoration: none; box-shadow:
none !important;
border: none;
border-radius: 8px !important;
}
91. https://matthewdeeprose.github.io/bluffer2020.html
Determine the relative luminance of
two colours.
https://www.w3.org/WAI/GL/wiki/R
elative_luminance
Compare the relative luminance of
the background and foreground
colour.
https://vanseodesign.com/web-
design/color-luminance/
How is colour contrast calculated?
See also https://planetcalc.com/7779/
94. https://matthewdeeprose.github.io/bluffer2020.html
Has an API to programmatically
calculate many ratios.
Suggests changes to a colour to
make it more accessible.
Online Colour Contrast Checkers
https://webaim.org/resources/contrastchecker/
https://accessible-colors.com/
95. https://matthewdeeprose.github.io/bluffer2020.html
You can now use the “Inspect
element” feature of your web
browser to check colour contrast.
See
https://developer.mozilla.org/en-
US/docs/Tools/Page_Inspector/How
_to/Inspect_and_select_colors
Local Colour Contrast Checkers
101. https://matthewdeeprose.github.io/bluffer2020.html
You have to run it on each page, so it
is more for impromptu checking.
It can find common issues,
particularly with text colours that
you may not have considered.
It does not check all aspects, for
example changes when you hover on
an element.
Automated Colour Contrast Checking… and more
104. https://matthewdeeprose.github.io/bluffer2020.html
Color Usage for Accessibility
WCAG 2.0 Level AA Contrast for Accessibility
12 pt Yes No Yes Yes Yes Yes Yes Yes No
18 pt Yes No Yes Yes Yes Yes Yes Yes No
12 pt Yes No Yes Yes Yes Yes Yes Yes No
18 pt Yes No Yes Yes Yes Yes Yes Yes No
12 pt No Yes Yes No No No No No Yes
18 pt No Yes Yes No No No No Yes Yes
12 pt No Yes Yes No No No No No Yes
18 pt No Yes Yes No No No No Yes Yes
Inspired by
Blackboard?
109. https://matthewdeeprose.github.io/bluffer2020.html
‘The :hover CSS pseudo-class
matches when the user interacts
with an element with a pointing
device, but does not necessarily
activate it. It is generally triggered
when the user hovers over an
element with the cursor (mouse
pointer).’
https://developer.mozilla.org/en-
US/docs/Web/CSS/:hover
https://css-
tricks.com/almanac/selectors/h/hover/
Hover in CSS
a:hover {
color: green;
text-decoration:
underline overline;
}
110. https://matthewdeeprose.github.io/bluffer2020.html
Hover / Selected states
Hover / selected text - Ratio:
8.48:1
Normal text - Ratio:14.44:1 /* Change Control Panel section colour as
seen by instructors */
.menuWrap-inner {
background: #002E3B !important;
color: #FFF }
#controlPanelPalette_contents a {
color: #FFF; }
/* Control Panel - hover over text colour */
#controlPanelPalette_contents a:hover {
color: #FCBC00 !important;
transition: all 0.2s ease-in-out !important; }
/* Controls color and format of open Control
Panel Items */
.controlpanel a.comboLink_active,
.controlpanel h4 a.open {
color: #FCBC00 !important; }
113. https://matthewdeeprose.github.io/bluffer2020.html
As you build and
develop your
customised theme, be
sure to consider colour
contrast.
Building your theme
empowers you to
ensure colour are “on-
brand” and that
contrast is
appropriate.
(Some of the built in
Blackboard colours do not
have sufficient contrast.)
For those of us who
still use the “Original
experience”, there are
still many benefits to
customising our
theme.
Colour contrast in summary.
I reported all
occurrences of poor
contrast to Bb support
that I found.
Check out my blog post
on the community site:
“Let me show you my
Blackboard.”
117. https://matthewdeeprose.github.io/bluffer2020.html
Course menus
• Cannot currently allow customisation of menu
whilst ensuring good contrast.
• Other options:
– Course Templates?
• Instructors may still change their colour
schemes after course creation.
• Rollover (course copy) may reset course
menu colours to that of source course.
– Don’t allow customisation?
118. https://matthewdeeprose.github.io/bluffer2020.html
Course menus…
– A community workaround for the sub header
colour not being configurable in the 2016
theme has been to set it as a specific colour.
– We set ours to black which does not
necessarily work with backgrounds other
than our default white colour.
/* Change colour of subheader */
#courseMenuPalette h3 span {
color: #000 !important;
}
119. https://matthewdeeprose.github.io/bluffer2020.html
From a current project
• A faculty wants a consistent menu, with
different colour schemes for their subject areas.
• The menu structure is done using course
templates.
• The menu colours are set by use JSHack to
– Load a CSS file that contains only details of
course menu.
– To appear only when in courses with certain
letters in the course id.
120. https://matthewdeeprose.github.io/bluffer2020.html
The CSS
/* Hide ability to change colour of menu */
li#menuDesignElement {
display: none; }
/* Change colour of subheader */
#courseMenuPalette h3 span {
color: #FEFEFE !important; }
/* Make subheader appear */
div.treeContainer ul.tree li.subhead h4.treeSubhead-collapsed a {
color: #FEFEFE !important; }
/* Make subheader rollover stay the same colour */
div.treeContainer ul.tree li.subhead h4.treeSubhead-collapsed hover {
color: #FEFEFE !important; }
/* Set menu background to brown */
#courseMenuPalette div.navPaletteContent, #courseMenuPalette_contents li {
background-color: #5a3737 !important; }
/* Set menu item text to #FEFEFE */
#courseMenuPalette div.navPaletteContent ul li a, #courseMenuPalette h3 a, #previewCourseMenu h3 a, .navPaletteContent h3
a.submenuLink:before, .navPaletteContent h3 a.submenuLink_active:before, #courseMenuPalette div.navPaletteContent ul li a span,
#courseMenuPalette .navPaletteContent .subhead { color: #FEFEFE; }
Hide option to change
menu colours ;-)
Easy to change all the
colour values to suit
your purposes.
123. https://matthewdeeprose.github.io/bluffer2020.html
/* Hide ability to change colour of menu */
li#menuDesignElement {
display: none; }
/* Change colour of subheader */
#courseMenuPalette h3 span {
color: #FEFEFE !important; }
/* Make subheader appear */
div.treeContainer ul.tree li.subhead h4.treeSubhead-collapsed
a {
color: #FEFEFE !important; }
/* Make subheader rollover stay the same colour */
div.treeContainer ul.tree li.subhead h4.treeSubhead-collapsed
hover {
color: #FEFEFE !important; }
/* Set menu background to brown */
#courseMenuPalette div.navPaletteContent,
#courseMenuPalette_contents li {
background-color: #5a3737 !important; }
/* Set menu item text to #FEFEFE */
#courseMenuPalette div.navPaletteContent ul li a,
#courseMenuPalette h3 a, #previewCourseMenu h3 a,
.navPaletteContent h3 a.submenuLink:before,
.navPaletteContent h3 a.submenuLink_active:before,
#courseMenuPalette div.navPaletteContent ul li a span,
#courseMenuPalette .navPaletteContent .subhead { color:
#FEFEFE; }
130. https://matthewdeeprose.github.io/bluffer2020.html
Keyboard Navigation on the web
Interaction Keystrokes
Navigate to most
elements
Tab
Shift + Tab - navigate backward
Link Enter
Button Enter or Spacebar
Checkbox Spacebar - check/uncheck a checkbox
Radio buttons
↑ / ↓ or ← / → = select an option.
Tab - move to the next element.
https://webaim.org/techniques/keyboard/
Deque Systems
UX Collective
139. https://matthewdeeprose.github.io/bluffer2020.html
‘The :focus CSS pseudo-class
represents an element (such as a
form input) that has received focus.
It is generally triggered when the
user clicks or taps on an element or
selects it with the keyboard's "tab"
key.’
https://developer.mozilla.org/en-
US/docs/Web/CSS/:focus
https://css-tricks.com/focusing-on-
focus-styles/
Focus in CSS
a:focus {
outline: 3px solid orange; }
141. https://matthewdeeprose.github.io/bluffer2020.html
9.2.26 Focus visible
Where ICT is a web page, it shall satisfy WCAG 2.0
Success Criterion 2.4.7 Focus Visible. Any keyboard
operable user interface has a mode of operation
where the keyboard focus indicator is visible.
…If the focus state relies on a change of colour (e.g.,
changing only the background colour of a button),
then changing from one colour to another that has
at least a 3:1 contrast ratio with the previous state of
the control is a method for meeting the Focus visible
criteria.
WCAG 2.1
The visual focus indicator … must have sufficient
contrast … except where the appearance of the
component is determined by the user agent and not
modified by the author.
https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html
WCAG 2.2 draft
2.4.11 Focus Visible (Enhanced)
https://www.w3.org/TR/WCAG22/#focus-visible-enhanced
Focus indicators in the regulations and guidelines.
Standard - EN 301 549
Accessibility requirements suitable for public
procurement of ICT products and services in
Europe
142. https://matthewdeeprose.github.io/bluffer2020.html
Level AA
When a User Interface Component
displays a visible keyboard focus, all
of the following are true:
• Minimum area: The focus
indication area is greater than or
equal to the longest side of the
bounding rectangle of the
focused control, times 2 CSS
pixels.
WCAG 2.2 Draft: 2.4.11 Focus Visible (Enhanced)
https://www.w3.org/TR/WCAG22/#focus-visible-enhanced
143. https://matthewdeeprose.github.io/bluffer2020.html
Level AA
When a User Interface Component
displays a visible keyboard focus, all
of the following are true:
• Focus contrast: Colour changes
used to indicate focus have at
least a 3:1 contrast ratio with the
colours changed from the
unfocused control.
WCAG 2.2 Draft: 2.4.11 Focus Visible (Enhanced)
https://www.w3.org/TR/WCAG22/#focus-visible-enhanced
144. https://matthewdeeprose.github.io/bluffer2020.html
Level AA
When a User Interface Component
displays a visible keyboard focus, all
of the following are true:
• Contrast or thickness: The focus
indication area has a 3:1 contrast
ratio against all adjacent colours
for the minimum area or greater,
or has a thickness of at least 2
CSS pixels.
WCAG 2.2 Draft: 2.4.11 Focus Visible (Enhanced)
https://www.w3.org/TR/WCAG22/#focus-visible-enhanced
145. https://matthewdeeprose.github.io/bluffer2020.html
Making focus indicators “on brand”
• Blackboard’s focus indicators have sufficient
contrast out of the box.
• When you customise the Blackboard theme to
use your institutional colours you should ensure
you update the focus indicators accordingly. Top tabs - Ratio: 7.36:1
Control Panel - Ratio: 7.36:1
154. https://matthewdeeprose.github.io/bluffer2020.html
When customising the Bb
responsive theme it
becomes almost inevitable
to deal with focus
indicators.
The default purple colours
often used in Blackboard
will not necessarily work
well with your institutional
colour scheme.
Customising Bb Focus indicators
Ratio: 1.72:1
156. https://matthewdeeprose.github.io/bluffer2020.html
Challenges
• Finding all the theme elements that you wish to
style can take some time, as without full
documentation it can be a lot of trial and error
whilst using inspect element.*
• Once I have tidied up my theme work I will share a
new version to the community site.
*See last year’s Bluffers guide for more about inspect
element.
157. https://matthewdeeprose.github.io/bluffer2020.html
9.2.16 No keyboard
trap
…ensure that keyboard users do
not become trapped in a subset
of the content that can only be
exited using a mouse or pointing
device.
9.2.20 Bypass blocks
…allow people who navigate
sequentially through content
more direct access to the
primary content of the Web
page.
9.2.22 Focus Order
…focusable components receive
focus in an order that preserves
meaning and operability.
9.2.29 On focus
…ensure that functionality is
predictable.
9.2.31 Consistent
navigation
…encourage the use of
consistent presentation and
layout for users who interact
with repeated content.
9.2.32 Consistent
identification
…ensure consistent
identification of functional
components that appear
repeatedly.
Not just focus (examples from EN 301 549)
162. https://matthewdeeprose.github.io/bluffer2020.html
All major operating
systems allow the user
to express a
preference for reduced
motion on-screen—
perhaps because they
have motion-triggered
vestibular spectrum
disorder.
We can detect
whether the user has
done this with the CSS
prefers-reduced-
motion media query.
Reducing motion
164. https://matthewdeeprose.github.io/bluffer2020.html
All major operating
systems allow the user
to express a
preference for reduced
motion on-screen—
perhaps because they
have motion-triggered
vestibular spectrum
disorder.
We can detect
whether the user has
done this with the CSS
prefers-reduced-
motion media query.
Reducing motion
@media (prefers-reduced-
motion: reduce) {
#puller.pullcollapsed a
{
animation: pulse 0s
infinite !important;
}
#puller.pullcollapsed
a:after {
animation: pulse2
0s infinite
!important;
}
}
Reducing motion
More info at: https://websitesetup.org/web-accessibility-checklist/
165. https://matthewdeeprose.github.io/bluffer2020.html
All major operating
systems allow the user
to express a
preference for reduced
motion on-screen—
perhaps because they
have motion-triggered
vestibular spectrum
disorder.
We can detect
whether the user has
done this with the CSS
prefers-reduced-
motion media query.
Reducing motion
@media (prefers-reduced-
motion: reduce) {
#puller.pullcollapsed a
{
animation: pulse 0s
infinite !important;
}
#puller.pullcollapsed
a:after {
animation: pulse2
0s infinite
!important;
}
}
Reducing motion
And https://elijahmanor.com/prefers-reduced-motion/
171. https://matthewdeeprose.github.io/bluffer2020.html
Agenda
Topic Why you should care
Ensuring equitable access to our learning
environment has never been more important.
The accessibility of our VLE matters even more when
our staff and students are relying on it for online
delivery.
Reflections on last year’s talk. This presentation builds on theme customisation, this
time with a focus on accessibility.
How the various web accessibility rules and
regulations are related.
I believe it is important to know how the recent EU
web accessibility regulations relate to the wider
standards of the W3C, and what changes we should
expect going forward.
Blackboard Theme accessibility considerations: Use
of Colour, Colour Contrast, Focus Indicators,
Movement, and Usability.
Practical examples of the application of the
regulations and standards within the context of Bb
theme customisation.
172. https://matthewdeeprose.github.io/bluffer2020.html
Conclusion
• Accessibility is a journey. There is always
something new to learn, and new
developments to understand.
• Customising our Blackboard theme still has
many benefits over staying with the defaults.
• In my experience colour contrast and focus
styles are the most important considerations
for Blackboard theme accessibility.
• With the techniques and suggestions shown
here you should feel confident to tackle these
in your theme.
173. https://matthewdeeprose.github.io/bluffer2020.html
Conclusion
• Accessibility is a journey. There is always
something new to learn, and new
developments to understand.
• Customising our Blackboard theme still has
many benefits over staying with the defaults.
• In my experience colour contrast and focus
styles are the most important considerations
for Blackboard theme accessibility.
• With the techniques and suggestions shown
here you should feel confident to tackle these
in your theme.
174. https://matthewdeeprose.github.io/bluffer2020.html
Conclusion
• Accessibility is a journey. There is always
something new to learn, and new
developments to understand.
• Customising our Blackboard theme still has
many benefits over staying with the defaults.
• In my experience colour contrast and focus
styles are the most important considerations
for Blackboard theme accessibility.
• With the techniques and suggestions shown
here you should feel confident to tackle these
in your theme.
175. https://matthewdeeprose.github.io/bluffer2020.html
Conclusion
• Accessibility is a journey. There is always
something new to learn, and new
developments to understand.
• Customising our Blackboard theme still has
many benefits over staying with the defaults.
• In my experience colour contrast and focus
styles are the most important considerations
for Blackboard theme accessibility.
• With the techniques and suggestions shown
here you should feel confident to tackle these
in your theme.