Chapter 4: Solid Structure: Built to Standards Flashcards

1
Q

When we talk about structural integrity for websites and software, what do we mean?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

If we have a solid structure…

A

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 well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How do you create solid structure

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Is validation possible to test purely by software?

A

No.

There are subjective aspects e.g. using alternative text correctly

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the advantages of using external css?

A

Separates presentation from content makes code more easier to understand
Adapt to different contexts and devices/media

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Whay are headings important to accessibility?

A

Screen readers often create a list of headings that can be navigated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly