Chapter 4: Solid Structure: Built to Standards Flashcards
When we talk about structural integrity for websites and software, what do we mean?
Websites that don’t break or have system failures
Functions in different contexts and on different devices
Adapt to the different ways they are accessed
If we have a solid structure…
People feel confident using the site as its stable, robust, and secure
Sites will work across different devices and technologies
Sites are more trustworthy
User needs and preferences are met
How do you create solid structure
Code content to be machine readable
Code to standards
Use standard Web technologies
Organise code for clarity and flow (show important information first and follow a logical, unbroken flow)
Use stylesheets to separate content and presentation
Use semantic markup for content
Is validation possible to test purely by software?
No.
There are subjective aspects e.g. using alternative text correctly
What are the advantages of using external css?
Separates presentation from content makes code more easier to understand
Adapt to different contexts and devices/media
Whay are headings important to accessibility?
Screen readers often create a list of headings that can be navigated