98-383 Introduction to Programming Using HTML and CSS Exam Guide
Exam 98-383, Introduction to Programming Using HTML and CSS, validates foundational ability to recognize and write syntactically correct HTML and CSS, structure content, and apply styles. It is aimed at learners building an entry-level understanding of web pages rather than experienced front-end specialists. This guide helps you decide whether your current skills match the published objectives, how to practise the tested tasks, and what to verify before attempting to schedule the exam.
What does exam 98-383 validate?
98-383 focuses on the relationship between HTML structure and CSS presentation. The published design places emphasis on writing correct markup, organizing information with HTML elements, understanding CSS syntax and precedence, and applying styles to a page. Treat it as a fundamentals assessment: you should be able to explain what code does and produce a small, coherent page without relying on copied fragments.
The official title is “Introduction to Programming Using HTML and CSS,” and its technology area is HTML and CSS. The published language version is HTML5 and CSS3. The exam is identified in the source document as an MTA credit-type exam, so candidates should distinguish this foundational credential from a broader professional web-development certification.
The objective document is more useful than a generic HTML tutorial because it describes practical implementation areas. It includes document structure, semantic elements, navigation, forms, multimedia, CSS stylesheets, selectors, precedence, and rule-set syntax. Preparation should therefore combine terminology review with repeated coding and inspection of working pages.
Who should consider this exam?
This exam suits a beginner, student, educator, or early-career candidate who needs a structured check of HTML and CSS fundamentals. It may also fit someone who has built simple pages informally and wants to identify gaps in standards-based markup, document structure, forms, navigation, and stylesheet application before moving to more advanced development.
The official preparation guidance expects approximately 100 hours of HTML and CSS instruction and/or hands-on experience. That figure is guidance, not a promise that every candidate needs the same amount of study. Someone who already writes and debugs small pages may need less directed learning; a learner who only edits templates may need more hands-on practice.
Microsoft Learn provides a beginner learning path with no listed prerequisites. Its modules cover building a first HTML webpage, using CSS styles, and learning basic web accessibility. That path is a sensible starting point for a new learner, but it should be supplemented with objective-by-objective practice because the exam source names areas such as forms, links, multimedia, and semantic markup in specific detail.
Do not use the exam title alone to judge readiness. A candidate who knows a few tags but cannot explain why a link fails, why a style is not applied, or how a form is structured should continue practising. Conversely, a learner who can create and correct small pages across the published areas may be using the exam at the appropriate level.
Which HTML skills are measured?
The HTML objectives require more than memorizing isolated element names. You should be able to build well-formed documents, choose suitable structural elements, connect pages and destinations, construct forms, and present common media. Practise each task in a complete page so that syntax, nesting, attributes, and relationships are tested together rather than as disconnected facts.
Document foundations and metadata
Review the purpose of the document structure and the role of metadata elements. Your practice should include a valid page skeleton, a meaningful title, appropriate head information, and correctly nested body content. The published skills specifically include HTML fundamentals, metadata elements, and well-formed markup.
A useful exercise is to take an intentionally damaged page and correct missing or mismatched tags, malformed attributes, and incorrectly nested elements. Then inspect the result in a browser and compare the source with the rendered page. This builds the habit of separating a browser’s forgiving rendering from genuinely well-formed markup.
Content structure and semantics
The objectives include headings, paragraphs, divisions, spans, lists, and tables. Learn the different structural jobs of these elements instead of treating them as interchangeable formatting tools. Build a page with a heading hierarchy, grouped content, an ordered or unordered list, and a small table whose headings and data are logically related.
HTML5 semantic elements are also listed: header, nav, section, article, aside, footer, details, summary, figure, and caption. Practise replacing generic containers with semantic elements when their meaning fits. For example, place site navigation in nav, an independent piece of content in article, and an explanatory image with its text in figure and caption.
Navigation and links
Navigation is an explicit objective area, including image links, anchors, targets, bookmarks, and relative or absolute links. Create a small multi-page site and add a navigation menu, a link to a location within a page, an image that functions as a link, and links that resolve from different folder locations.
The main pitfall is confusing what a link displays with where it points. Check the href value, the target behavior, fragment identifiers, and the relationship between the current document and a relative path. Test links after moving a page into a subfolder; this reveals path assumptions that may remain invisible in a single-file exercise.
Use absolute URLs only when an external destination is intended. For pages within your project, practise relative links and verify them from the actual file location. This is a study recommendation based on the published navigation objectives, not an additional official requirement.
Forms and controls
The published skills include form attributes and controls such as action, method, input types, select, textarea, button, output, option, datalist, and fieldset. Build a form that groups related fields, offers several input types, includes selectable options, and has a clearly defined submission control. Be able to identify which element collects data and which attribute or control influences submission behavior.
Practise reading a form from the outside in: identify the form boundary, determine its action and method, inspect each control’s type and name-related information, then check grouping and available options. Do not study forms as a list of tag definitions. Ask what information the user is entering, how it is grouped, and how the browser presents the control.
A common mistake is to confuse visual appearance with form semantics. A styled text box is not automatically the same as a control with a particular input type, and a visible label-like phrase does not replace correctly structured form content. Use the browser to test controls, but also inspect the source so you know which markup produced the behavior.
Multimedia and embedded content
The objectives cover img, picture, SVG, canvas, video, audio, track, source, and simple iframe implementations. Prepare small examples that show how each element is used and what supporting elements or attributes are relevant. The goal is not to become a media specialist; it is to recognize the structure and purpose of basic HTML media implementations.
Compare img and picture in a controlled page, then examine how source entries support media choices. Add a video or audio element with a source, and inspect how a track can provide timed text. Create simple SVG and canvas examples without turning the exercise into a graphics project. Include an iframe only for a straightforward embedded-content scenario.
Accessibility should remain part of this practice. Microsoft Learn’s beginner path explicitly includes web accessibility, so review meaningful text alternatives and usable structure alongside the element syntax. This is especially valuable because a page can render successfully while still communicating poorly to users or assistive technology.
Which CSS skills are measured?
CSS preparation should cover both syntax and the process used to determine which declaration wins. The published objectives name inline, internal, and external stylesheets, precedence, selectors, and rule-set syntax. Build styles in all three locations, inspect the result, and explain why a particular property value is applied instead of relying on trial and error.
Stylesheet placement and application
Create the same simple page with an inline declaration, an internal style block, and an external stylesheet. Observe how the location of each declaration affects maintenance and how competing rules are resolved. You should be able to recognize the difference between a style written on an element, a style embedded in the document, and a style loaded from another file.
A practical exercise is to remove the external stylesheet link, alter the path, and introduce a deliberate syntax error. Record what stops working and what remains visible. This trains you to distinguish a loading problem from a selector mismatch or an invalid declaration.
Selectors, declarations, and rule sets
Review the structure of a rule set: a selector identifies elements, declarations specify properties and values, and punctuation separates the parts. Practise element, class, and id selections, then combine them in a small page with repeated components and one uniquely identified region.
Write a prediction before refreshing the page: which elements should change, which should remain unchanged, and which rule should apply when selectors overlap? Compare the prediction with the browser’s rendered result and inspect the computed styles. This makes selector reasoning an active skill rather than a memorization exercise.
Watch for small syntax errors that produce large effects, including a missing brace, incorrect separator, misspelled property, or malformed value. Keep a clean version of each exercise so you can compare a broken rule with a corrected one.
Precedence and debugging
Precedence is a likely source of avoidable errors because a syntactically valid declaration can still lose to another applicable rule. Practise changing one factor at a time: selector specificity, source order, stylesheet location, or an inline declaration. Your explanation should identify the competing rules and the reason the winning declaration is used.
Use browser developer tools as a learning aid, not as a substitute for understanding. Select an element, inspect the styles, and read which declarations are active or crossed out. Then reproduce the result by reasoning from the source. Keep notes for recurring mistakes, such as targeting a parent when the intended element is a child or assuming later source order always overrides every other consideration.
Avoid making every conflict disappear with excessive overrides. That may fix a demonstration page while concealing the underlying rule-resolution problem. For exam preparation, a smaller page with deliberately competing rules is more useful than a large project whose styles are difficult to trace.
How should you turn the objectives into practice?
Use a build-and-explain cycle: read one objective, create a small implementation, break one part deliberately, repair it, and explain the result in plain language. This approach covers recognition and writing, which the published exam design expects, while producing evidence that you can work without depending on memorized answer patterns.
Start with a diagnostic page
Before following a long study schedule, create a compact site from a blank folder. Include a well-formed document, metadata, headings, paragraphs, a list, a table, semantic sections, a navigation area, one internal bookmark, a form, and a small media example. Add an external stylesheet with several selectors and intentional style conflicts.
Do not grade yourself by whether the page looks attractive. Instead, make a checklist of tasks you could not complete, concepts you could not explain, and errors you could not locate. Those observations determine the first study block more reliably than a general feeling that HTML or CSS is familiar.
Study in dependency order
Learn document structure and well-formed markup before concentrating on multimedia or advanced styling. Then move through semantic structure, links, forms, and media; study CSS placement and syntax before spending time on precedence and debugging. This order reflects how later tasks depend on a reliable page and a clear separation between content and presentation.
After each topic, add it to the same small project. A navigation exercise should use the document structure you already understand; a form exercise should fit inside a semantic page; a stylesheet exercise should style real headings, controls, and media. Reusing the project creates integration practice without requiring a large application.
Explain every correction
When a page fails, write a short cause-and-fix note. Examples include “the fragment identifier does not match the destination id,” “the relative path is based on the current file,” or “the selector does not match the element.” If you cannot explain the correction, repeat the exercise with fewer moving parts.
This habit is particularly useful for multiple-choice or code-reading situations. The correct option is easier to identify when you can trace markup structure, attribute purpose, selector matching, and style precedence rather than recognizing a familiar-looking snippet.
What should a practical study roadmap look like?
A flexible roadmap should move from foundations to integrated implementation and then to timed review. Allocate study according to your diagnostic results rather than dividing time evenly across topics. The official preparation guidance gives approximately 100 hours of instruction and/or hands-on experience as a reference point; the schedule below is a sequence, not a claim about a required personal duration.
Phase one: establish the page model
Begin by learning how a browser interprets an HTML document. Practise metadata, well-formed markup, headings, paragraphs, divisions, spans, lists, and tables. Create pages from scratch and repair malformed examples. At the end of this phase, you should be able to describe the document tree and choose an element for a content purpose.
Use the Microsoft Learn beginner path as an accessible starting resource. Its first module addresses writing a basic HTML page, and its later modules connect CSS styling with accessibility. Keep the official objective document beside the lessons so you can mark which exam areas have been covered and which still need separate exercises.
Phase two: build meaningful HTML features
Next, implement semantic elements, navigation, forms, and multimedia. Make each feature work in a small project: navigate between pages and bookmarks, submit a form in a test setting, group controls, and add basic media and embedded content. Inspect source and browser output after every change.
At this stage, spend extra time on distinctions that are easy to blur: relative versus absolute links, a page fragment versus a separate page, a generic container versus a semantic element, and an input control versus a visual decoration. These distinctions are more useful than copying a finished template.
Phase three: apply and troubleshoot CSS
Create internal and external stylesheets and use inline styles only as a comparison point. Practise selectors and rule-set syntax, then introduce competing declarations and determine which one wins. Debug missing stylesheet links, unmatched selectors, malformed declarations, and unexpected precedence.
Keep the HTML stable while changing CSS so that each result has a clear cause. Then keep the CSS stable while changing one HTML attribute or class. This separation helps you identify whether the problem is in the document, the selector, the stylesheet connection, or the declaration itself.
Phase four: integrate and review
Finish with a small accessible site that combines the published skill areas. Review it against a written checklist rather than judging only the visual result. For each objective, mark whether you can recognize correct code, write a working example, and diagnose a broken example.
Use short review sessions to revisit error notes, not to reread everything from the beginning. If a topic remains weak, return to a minimal exercise and rebuild it. Avoid spending the final preparation period on unofficial “likely questions” or answer collections; they do not demonstrate reliable ability and may not reflect the published objectives.
How can you check readiness without exam dumps?
Readiness is best demonstrated by independent implementation and explanation. Put away notes and build a small page from a written specification, then inspect and repair it. You are closer to ready when you can handle unfamiliar combinations of the listed skills, not merely reproduce a tutorial’s exact example.
Use an objective checklist
Create rows for HTML fundamentals and metadata, well-formed markup, document structure, semantic elements, navigation, forms, multimedia, CSS stylesheet types, selectors, precedence, and rule-set syntax. For each row, record a working example, a broken example you repaired, and a one-sentence explanation of the relevant rule.
The checklist should expose omissions. A learner may be comfortable with headings and paragraphs but have never used datalist, fieldset, track, picture, or an internal bookmark. Those are not reasons to panic; they are signals to create focused exercises from the published skills list.
Use code-reading drills
Take a short HTML or CSS fragment and predict its result before opening it in a browser. Identify the document structure, link destination, form control, selector matches, and competing declarations. Then verify the prediction and explain any difference.
Keep the fragments small enough to reason about. Large copied pages encourage visual guessing and make it difficult to identify the exact cause of a result. A series of focused drills gives better feedback about whether you understand syntax and behavior.
Use build constraints
Give yourself a requirement such as “create two pages with a shared external stylesheet, one same-page bookmark, a semantic article, a grouped form, and one media element.” Work from a blank file and do not paste a solution. Afterward, remove or alter one part and repair the result.
This method tests transfer. It also reveals whether you know how features connect: a link must point somewhere meaningful, a selector must match the markup, and a stylesheet must be available to the document.
What mistakes commonly waste preparation time?
The most expensive mistakes are not usually obscure syntax errors; they are study decisions that hide weak understanding. Candidates often read broad tutorials without mapping them to the objectives, practise only visual styling, ignore links and forms, or treat a page that renders as proof that its markup is correct.
Studying appearance instead of structure
A page can look acceptable while using poor structure or an ineffective selector. During preparation, inspect the source and ask whether the element communicates the intended role, whether the markup is well formed, and whether the style rule matches the intended target. Visual polish should come after structural correctness.
Memorizing element lists without using them
Knowing that an element exists is weaker than knowing when and how to use it. Convert every unfamiliar objective term into a small implementation. For example, add details and summary to an expandable section, use figure and caption for a media example, and construct a fieldset around related form controls.
Ignoring file and path context
Link and stylesheet failures often come from the relationship between files, not from the element name. Move a page into a subdirectory, update its relative paths, and test again. This makes the distinction between relative and absolute links concrete and gives you a repeatable debugging method.
Treating unofficial questions as a syllabus
Third-party question collections can be incomplete, outdated, or unauthorized. They cannot replace the official objectives, and memorizing answers does not establish that you can write or debug HTML and CSS. Use the published skills and your own working pages as the preparation baseline.
What delivery information should you verify before scheduling?
The published exam document identifies VUE and Certiport as exam providers and lists language availability in English, Japanese, Traditional Chinese, Simplified Chinese, Spanish, Portuguese-Brazilian, French, German, and Korean. Confirm current registration, provider, availability, and candidate-account instructions directly with the official provider before making plans because catalogue and scheduling information can change.
Check whether an appointment is currently available
The current Certiport MTA objectives page retrieved for this research lists other MTA exams but does not show 98-383 among the displayed exams. A Microsoft Q&A post also contains a user statement that 98-383 was retiring and that vouchers were no longer sold, but that post is not sufficient evidence for a current official retirement determination.
Before paying, travelling, or committing to a study deadline, search the official Certiport and relevant provider pages for the exam and verify that registration is actually offered. If it is not listed, contact the provider or official certification support rather than relying on an old listing, forum comment, or reseller claim.
Resolve account or scheduling problems through official support
An archived Microsoft Q&A response about a scheduling-access problem suggested trying Edge or Internet Explorer version 9 or above, clearing cache and cookies, using an InPrivate session, and contacting Pearson VUE Support if the issue continued. These are historical troubleshooting instructions, so first use the current provider’s supported browser and support guidance.
If an account cannot access scheduling, record the exact error, confirm that the exam is currently listed, and use the official certification or provider support route. Do not create duplicate accounts or buy an exam attempt from an unverified source while the identity or scheduling issue is unresolved.
Keep result records and support contacts
A Microsoft Q&A thread describes a candidate asking about a missing confirmation or certificate and directs exam-result questions to certification profile, dashboard, or score-report support forums. This is evidence that support routes matter, not a guarantee about when results or credentials will arrive.
Save the appointment confirmation, provider details, and any score report supplied through the official channel. If a result or certificate is missing, use the support route associated with the provider and certification profile rather than treating a forum post or reseller message as authoritative.
What should you do next?
First, verify that 98-383 can currently be scheduled through an official provider. If availability is confirmed, download or review the official objective document, complete a diagnostic page, and begin with the weakest prerequisite area. If availability cannot be confirmed, continue learning the published HTML and CSS skills while treating the exam as a planning reference rather than assuming an appointment exists.
A practical first session
Create a blank project with one HTML file and one CSS file. Add metadata, headings, paragraphs, a semantic navigation area, a list, a table, and a link to a page bookmark. Connect the external stylesheet and style at least several different element types. Write down every uncertainty instead of searching immediately; investigate the list after the first attempt.
A practical weekly review
At the end of each study cycle, rebuild one feature without notes and repair one deliberately broken example. Rotate among structure, links, forms, multimedia, selectors, and precedence so that a strong topic does not crowd out an objective you have not yet implemented. Update your checklist with evidence, not confidence alone.
The final decision
Schedule only after checking current official availability and after your practice shows independent implementation across the objective areas. If you still depend on copied snippets, cannot explain why a style wins, or regularly lose track of link paths and form structure, postpone the attempt and target those weaknesses with smaller exercises.
Conclusion
98-383 is best approached as a practical HTML and CSS fundamentals assessment: build pages, inspect the markup, test links and controls, apply styles, and explain the browser’s result. Use the official objectives as the boundary of study, Microsoft Learn as a beginner-friendly starting point, and current provider pages as the authority for scheduling and availability. Verify those operational details before committing to an exam date, then let a diagnostic project and objective checklist determine the remaining preparation.
