Skip to content

AccessibilityProject - Linda L #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
llindallarsson wants to merge 12 commits into
base: main
Choose a base branch
from
Open

AccessibilityProject - Linda L #44

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
f98a889
basic html for the quiz
llindallarsson Mar 27, 2025
cbb3a19
basic styling for body, header and main
llindallarsson Mar 31, 2025
f866f2a
main menu styling
llindallarsson Mar 31, 2025
14b660f
function for displaying questions
llindallarsson Mar 31, 2025
1db6a5b
page navigation added in JS
llindallarsson Apr 2, 2025
0583ef5
basic functionality
llindallarsson Apr 2, 2025
77ef529
Functions like progressbar, next-question button and error-message fixed
llindallarsson Apr 3, 2025
4264368
progressbar fixes
llindallarsson Apr 3, 2025
1f83afe
focus tabing on quiz
llindallarsson Apr 3, 2025
b4e24c0
added content
llindallarsson Apr 3, 2025
5b6a551
responsive CSS and cleaned JS
llindallarsson Apr 6, 2025
79c3cab
CSS cleaned and screen reader fixes
llindallarsson Apr 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added .DS_Store
View file
Open in desktop
Binary file not shown.
168 changes: 166 additions & 2 deletions about.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,174 @@
<!DOCTYPE html>
<html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>About</title>
<link rel="stylesheet" href="css/styles.css" />
</head>
<body></body>

<body>
<a href="#main-content" class="skip-link"> Skip to main content </a>

<header id="header">
<div class="header-content">
<h1>Web Accessibility Quiz</h1>
<nav role="navigation" aria-label="Main navigation">
<ul>
<li>
<a href="index.html">Home</a>
</li>
<li class="active">
<a href="about.html" aria-current="page">About</a>
</li>
</ul>
</nav>
</div>
</header>

<main id="main-content">
<section id="about" class="about-section">
<div>
<h2>About Web Accessibility & WCAG</h2>
<p>
The internet should work for everyone—but many digital experiences
still fall short when it comes to accessibility. That’s where the
<b>Web Content Accessibility Guidelines (WCAG)</b> come in.
</p>
</div>
<div>
<h3>What is WCAG?</h3>
<p>
WCAG is a globally recognized standard developed by the
<b>W3C (World Wide Web Consortium)</b> to help make websites, apps,
and digital content accessible to users of all abilities. These
guidelines are essential for building inclusive interfaces that
consider users with visual, auditory, motor, cognitive, and
neurological impairments. <br /><br />

WCAG is built around four key principles, known as <b>P.O.U.R.</b>:
</p>
</div>
<div>
<h3>WCAG POUR Principles</h3>

<div class="educational-images">
<img
src="img/WCAG-POUR.png"
alt="Diagram illustrating the four WCAG accessibility principles: Perceivable, Operable, Understandable, and Robust, with key characteristics listed under each."
/>
</div>
</div>
<div>
<div>
<h4>Perceivable <span aria-hidden="true">👀</span></h4>
<p>
Users must be able to detect and interpret content, regardless of
how they consume it.
</p>
</div>
<div>
<p><b>As a developer, this means:</b></p>
<ul>
<li>Use semantic HTML and provide alt attributes for images.</li>
<li>
Ensure text has sufficient color contrast against backgrounds
(e.g., using WCAG AA or AAA contrast ratios).
</li>
<li>Add captions and transcripts for multimedia content.</li>
</ul>
</div>
</div>

<div>
<div>
<h4>Operable <span aria-hidden="true">🎮</span></h4>
<p>
All users should be able to navigate and interact with your
interface.
</p>
</div>
<div>
<p><b>To support this, you should:</b></p>
<ul>
<li>
Ensure full keyboard functionality (e.g., forms, buttons,
menus).
</li>
<li>Provide visible focus indicators and logical tab order.</li>
<li>
Avoid flashing content that could trigger seizures or
discomfort.
</li>
</ul>
</div>
</div>
<div>
<div>
<h4>Understandable <span aria-hidden="true">🧠</span></h4>
<p>
Your content and interface should be predictable, clear, and
helpful.
</p>
</div>
<div>
<p><b>This includes: </b></p>
<ul>
<li>Using clear, simple language</li>
<li>Ensuring consistent design and predictable behavior</li>
<li>
Offering helpful error messages and instructions for forms and
interactions
</li>
</ul>
</div>
</div>
<div>
<div>
<h4>Robust <span aria-hidden="true">🔧</span></h4>
<p>
Your code should be compatible with a wide range of
technologies—including screen readers and future tools.
</p>
</div>
<div>
<p><b>Best practices:</b></p>
<ul>
<li>Use clean, semantic HTML over div-based structures.</li>
<li>
Avoid unnecessary ARIA roles—use native elements where possible.
</li>
<li>
Ensure dynamic content updates are accessible (e.g., using ARIA
live regions).
</li>
</ul>
</div>
</div>
<div>
<p>
By following the <b>P.O.U.R. principles</b>, you build more
resilient, inclusive, and future-proof digital experiences.
Accessibility isn’t just a nice-to-have—it’s essential for reaching
all users, and it’s part of writing good code.
</p>
</div>
</section>
</main>

<footer role="contentinfo">
<div class="footer-content">
<nav role="navigation" aria-label="Footer navigation">
<ul>
<li>
<a href="index.html">Home</a>
</li>
<li>
<a href="about.html">About</a>
</li>
</ul>
</nav>
</div>
</footer>
</body>
</html>
Loading