SILS iSchool

12 Feb 2019

meets Tuesday and Thursday from 0800-0915

in Carolina Hall 220

Contact options

office hours in Manning 112


Value Added | daily

Class Schedule

Basics | sessions 01-05

10 Jan | intro
15 Jan | clients
17 Jan | servers
22 Jan | networks
24 Jan | basics lab

Web Development | sessions 06-11

29 Jan | structural layer
31 Jan | presentational layer
05 Feb | working with layers
07 Feb | behavior layer |
12 Feb | images & design | design thoughts | accessible design | next session
14 Feb | website lab

Document Markup | sessions 12-14

19 Feb | document markup
21 Feb | tools that read markup
26 Feb | document markup lab

Spreadsheets | sessions 15-19

28 Feb | spreadsheets
05 Mar | formulas & functions
07 Mar | data display

 09-17 Mar | Spring Break 

19 Mar | database tools
21 Mar | spreadsheets lab

Relational Database | sessions 20-26

26 Mar | relational databases
28 Mar | tables
02 Apr | relationships
04 Apr | input & output
09 Apr | SQL
11 Apr | complex queries
16 Apr | databases lab

Presentation | sessions 27-30

18 Apr | presentation design
23 Apr | presentation delivery
25 Apr | presentation lab
30 Apr | 0800-1100 | final in class presentation





Ensure that your design affords accessibility to the broadest spectrum of users.

What is Web Accessibility?

Web accessibility means that people with disabilities can use the Web. More specifically, Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web.

[W3C model of usability and accessibility]

W3C Web Accessibility Initiative

In summary:

Perceivable

  • Provide text alternatives for non-text content.
  • Provide captions and other alternatives for multimedia.
  • Create content that can be presented in different ways, including by assistive technologies, without losing meaning.
  • Make it easier for users to see and hear content.

Operable

  • Make all functionality available from a keyboard.
  • Give users enough time to read and use content.
  • Do not use content that causes seizures.
  • Help users navigate and find content.

Understandable

  • Make text readable and understandable.
  • Make content appear and operate in predictable ways.
  • Help users avoid and correct mistakes.

Robust

  • Maximize compatibility with current and future user tools.

back to top

back to top