INF-306 Exam Dumps - HTML5 Application Development

@media screen and (max-width: 480px) {

/* style rules go here */

}

The correct media query is @media screen and (max-width: 480px) {. The requirement says the style rule must apply to screen devices with a width of 480 pixels or less. In CSS media queries, screen identifies the media type, and (max-width: 480px) defines the upper viewport-width limit. This means the enclosed CSS rules apply when the viewport is 480 pixels wide or any smaller value, which is the standard mobile breakpoint behavior. @media screen and (width: 480px) is incorrect because it applies only when the viewport is exactly 480 pixels wide, not below it. @media screen display and (width: 480px) is invalid syntax because display is not used that way in a media query. @media screen-width: 480px is also invalid because it does not follow the required @media media-type and (feature: value) pattern. References/topics: responsive design, CSS media queries, @media, screen media type, max-width, mobile breakpoint styling.

The two likely causes are undersized touch targets and overlapping input regions. Touch input is less spatially precise than mouse input because the contact area of a finger is larger and less exact than a pointer cursor. Microsoft’s touch-target guidance states that interactive UI elements must be large enough for users to access accurately, and recommends a target size around 7.5 mm square, approximately 40 × 40 pixels on a 135 PPI display. Earlier Microsoft touch-design guidance similarly emphasizes that controls must be appropriately sized for touch and identifies approximately 9 mm as a minimum targeting area. Therefore, small input buttons may fail to trigger because the user is not actually hitting the active target area. Overlap is also a valid cause: when two active regions occupy the same physical screen area, hit testing may route the touch to a different element, or the effective target area may be reduced. W3C accessibility guidance explicitly treats overlapping targets as reducing measurable target size unless the overlapping controls perform the same action. Event handlers themselves are not the defect; they are the normal mechanism for processing input. “Touch screen not initialized” is not a standard HTML5 application cause. References/topics: touch input, event handling, hit testing, target size, overlapping controls.

The correct transformation functions are matrix() and skew(). CSS transformations are applied with the transform property and accept transform functions that alter an element’s rendered appearance in two-dimensional or three-dimensional space. MDN defines < transform-function > as a data type representing a transformation that can rotate, resize, distort, or move an element in 2D or 3D space. The matrix() function is valid because it defines a homogeneous two-dimensional transformation matrix, allowing translation, scaling, rotation, and skewing effects to be represented numerically in one function. The skew() function is also valid because it explicitly skews an element on the 2D plane. scroll() is not a CSS transform function; scrolling is handled through overflow behavior or scrolling APIs. move() is also not a valid CSS transform function; the standard transform function for movement is translate(). References/topics: CSS3 transforms, transform property, 2D transformation functions, matrix(), skew().

==========

The correct markup is option D. The type= " tel " input type is appropriate for telephone-number entry, but it does not automatically validate a specific telephone-number format because phone formats vary internationally. MDN notes that tel inputs allow telephone entry but are not automatically validated to a particular format. Therefore, a pattern attribute is required to enforce the exact structure. The regular expression [0-9]{3}-[0-9] {3}-[0-9]{4} requires three digits, a hyphen, three digits, another hyphen, and four digits, matching the requested format such as 111-444-7777. MDN defines the pattern attribute as a regular expression the input value must match for constraint validation. The required attribute is also necessary because the field must not be empty; MDN states that required indicates the user must specify a value before the form can be submitted. Option A only limits length. Option B lacks hyphen validation and required. Option C hard-codes only specific digits. References/topics: HTML5 validation, tel, pattern, required, regular expressions.

==========

The paragraph containing the text Tigers will display first.

False

The section p CSS refers to the parent flexbox container.

False

When the paragraphs have a width less than 200px, the last paragraph will wrap to the next line.

True

The parent flexbox container is the section element because it has display: flex;. The paragraphs inside the section become flex items. The display order is controlled by each paragraph’s inline order value, and flex items are laid out from the lowest order value to the highest. Therefore, Zoo Trip with order: 1 displays first, followed by Bears, Lions, and finally Tigers; the statement that Tigers displays first is false. The selector section p does not refer to the parent flexbox container. It targets paragraph elements inside a section, meaning it styles the flex items, not the flex container. The container itself is targeted by the section rule. The final statement is true in intent because flex-wrap: wrap; allows flex items to move to a new line when they cannot fit in the available row. Since each paragraph has min-width: 200px, items are prevented from shrinking below that minimum and wrapping occurs when available space is insufficient. References/topics: CSS flexbox, flex container, flex items, order, flex-wrap, min-width.