3. Two Concepts in Content Accessibility
1) Semantics, or the construction of meaning through
structure.
2) Alternatives, or the opportunity to access content in a
different format.
4. Semantics and Structure
1) What is "meaning" in code?
2) How does HTML code define the meaning of content?
7. HTML Elements Have Meaning
1) <header> or <div role="banner">
2) <nav> or <div role="navigation">
3) <main> or <div role="main">
4) <aside> or <div role="complementary">
5) <footer> or <div role="footer">
8. Semantics within content
1) Headings - <h1>, <h2>, etc.
2) Lists - <ul>, <ol>
3) Forms and inputs - <form>, <input>, etc.
4) Buttons - <button>, <input type="submit">
5) Links - <a href="http://example.com">
6) Tables - <table>
9. Separation of Content and Design
- CSS (Cascading Style Sheets)
- Provides design for visual structures
- HTML
- Provides semantics for non-visual structure
16. Interactive Content
- Composite of all other types of content
- Dynamic feedback and communication
- ARIA: Accessible Rich Internet Applications
17. Making Good Choices
1) Design decisions and HTML choices should match.
2) HTML creates meaning and relationships on the page.
3) What you see should be what you get.
Are you meeting your accommodation requirements? Learning about job, applying for job, performing job.
Ability to get in; ability to find your way around; ability to complete necessary tasks in the virtual space.
Physical building: ramps, wayfinding and tactile maps, grab bars and roll-in showers.
Can a user use the navigation provided? Do they know what page they're on and where they are on the page? Can they accomplish their goals
CSS is powerful and flexible, but can also disguise the truth behind the code: what looks like a heading may not be a heading.