Chapter 3 - Some Big Concepts You Need to Know Flashcards
progressive enhancement
one strategy for dealing with unknown browser capabilities - start with a baseline experience that makes the content or core functionality available to even the most rudimentary browsers or assistive devices - then layer on more advanced features for the browsers that can handle them - finish with nice to have effects that enhance the experience for users with the most advanced browsers
graceful degradation
where you design the fully enhanced experience first, then create a series of fallbacks for non-supporting browsers
authoring strategy
writing an HTML document in logical order, and elements marked up in an meaningful way, also ensures search engines will catalog the content correctly
styling strategy
create layers of experiences by taking advantage of the way browsers parse style sheet rules
scripting strategy
making sure basic functionality is intact even when JavaScript is turned off.
Responsive Web Design (RWD)
strategy for providing appropriate layouts to devices based on the size of the viewport
M-dot Sites
separate mobile sites with customized interface and features set
accessibility
building pages in a manner that creates as few barriers as possible to getting to information, regardless of the user’s ability and the device used to access the web
vision impairment
people with low or no vision
mobility impairment
users with limited or no use of their hands
auditory impairment
users with limited or no hearing
cognitive impairment
users with memory, reading comprehension, problem solving, or attention limitations
Web Accessibility Initiative (WAI)
created by the W3C to address the need to make the web usable for everyone
Web Content Accessibility Guidelines (WCAG)
a document produced by the WAI to help developers create accessible sites
Accessible Rich Internet Applications (WAI-ARIA)
a spec that addresses the accessibility of web applications that include dynamically generated content, scripting, and advanced interface elements that are particularly confounding to assistive devices - defines a number of roles for content and widgets that authors can explicitly apply using the role attribute
waterfall chart
a chart that shows you all the requests made and assets downloaded
List at least two unknown factors you need to consider when designing and developing a site.
- the size of the screen or browser window
- the user’s internet connection speed
- whether JavaScript is enabled
- Whether the browser supports specific features
- Whether the user is at a desk or on the go (context and attention span)
Match the technology or practice with the problem it best addresses: Progressive enhancement
All levels of browser capabilities
Server-side detection
Determining which device is being used
Responsive design
A variety of screen sizes
WAI-ARIA
Assistive reading and input devices
Site performance optimization
Slow connection speeds
Web accessibility strategies take into account four broad categories of disabilities. Name the four and provide a measure you might take to ensure content is accessible for each.
Sight impairment: make sure the content is semantic and in logical order for when it is read by a screen reader.
Hearing impairment: provide transcripts for audio and video content.
Mobility impairment: use measures that help users without a mouse or keyboard.
Cognitive impairment: content should be simple and clearly organized.
When would you use a waterfall chart?
You would use a waterfall chart to evaluate your site’s performance in the optimization process.
