- Covers FSS Considerations (see below)
- CSS Reset / Normalization
- Responsive layouts using grid or column schemes
- Push-pull control
- Special text boxes and labels - alerts, warnings, notes, wells, pre-formatted boxes etc.
1 Implemented using Sections - not Unordered List.
2 Dropdown is a JS plugin that can be attached to almost any content, not just lists.
- Navigation lists: can be mixed with pills and dropdowns, dividers / spacers, flexible tabs placement
The following classes are used by UIO and Exploration Tool:
Links and Text:
Hypothetical Scenario: Framework as FSS Replacement
To better understand functionality of a framework, it may be worthwhile to explore how a framework can replicate functionality of FSS (see: FSS Cheat Sheet).
forms and controls
- Apply button styling to an element
- Purecss - add pure-button class to anchor element to make it into a button.
- alignment: left, right
- control and label alignment: left, center, right
- movable containers that emcompass elements that collectively create a "widget" (i.e. a calendar or search field).
- Foundation - Foundation has a Panel style which is like a callout.
- contains: title, options, and content sections.
- progressive enhancement
- visibility / content hiding
- 5 modes of hiding:
- hidden to browsers and ATs
- hidden to browsers and ATs, but maintaining layout
- hidden to browsers but available to ATs
- hide text and replace with image
- size, spacing between characters
- Bootstrap - defined via
- font loading: serif, sans, monospace, times, courier, arial, verdana
- alignment: left, right, center
- very minimal
- written in SMACSS
- Purecss is designed to play nice with other frameworks. One use case is to have Purecss as foundation and specific Bootstrap modules.
- Flexible layouts like the other frameworks
- Can specify equal height grids that are backward compatible with IE (except IE7)
- documentation can be technical. Examples can be hard to follow as they often consist of just CSS snippets.
- has clearfix
- Of all the frameworks, YAML is the only one to address accessibility interests:
- cross-browser implementation of skip links (to navigation and content).
- different layers of visibility:
- visually hidden, but accessible
- visually hidden but visible to ATs and print
- hidden on print, but visible on all other media.