RFC 7993: Cascading Style Sheets (CSS) Requirements for RFCs
In plain English — editorial summary, not part of the RFC
The HTML format for RFCs assigns style guidance to a Cascading Style Sheet (CSS) specifically defined for the RFC Series. The embedded, default CSS as included by the RFC Editor is expected to take into account accessibility needs and to be built along a responsive design model. This document describes the requirements for the default CSS used by the RFC Editor. The class names are based on the classes defined in "HTML for RFCs" (RFC 7992).
Document record
- Document ID
- RFC7993
- Published
- December 2016
- Authors
- H. Flanagan
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 14
- Also known as
- —
- Updated by:
- RFC 9920
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7992HTML Format for RFCsUpdated
December 2016
- RFC 7994Requirements for Plain-Text RFCsUpdated
December 2016
- RFC 7995PDF Format for RFCsUpdated
December 2016
- RFC 7991The "xml2rfc" Version 3 VocabularyUpdated
December 2016
- RFC 7996SVG Drawings for RFCs: SVG 1.2 RFCObsoleted
December 2016
- RFC 7990RFC Format FrameworkObsoleted
December 2016
- RFC 7997The Use of Non-ASCII Characters in RFCsUpdated
December 2016
- RFC 7998"xml2rfc" Version 3 Preparation Tool DescriptionCurrent
December 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?