CR1-S06 · Mi vida digital · Learn

Back to your course / CR1-S06

Computing and Robotics · 1.º ESO · Learn

My digital life

In twelve paired sessions you will investigate what posts reveal, how to protect access and files and how to seek support. Turn reasoned decisions into a local web guide. Cases and profiles are fictional; neither personal experiences nor audits of classmates’ accounts are needed.

12 planned lessonsCR1-S06
Understand the idea. Design, test and explain your solution.

Your mission

Create the ‘Web guide to a safe digital life’: three linked local pages covering privacy, protection and response, wellbeing and credits. Include justified guidance for six cases, permitted accessible images, checked links and a protection plan. Demonstrate a fictional-profile adjustment, reader permissions and recovery of a practice file; share only within the school’s restricted environment.

Original illustration of students planning and testing a computing project.
Ilustración original de apoyo visual · Sintaxis Divergente, 2026.

Read the explanation, study the diagram and try the activity in each section. You can choose another version at any time.

Your tools

Use Google Docs for written explanations and diagrams.net for diagrams. Save the editable file as well as the evidence requested in each task.

6.1. Footprint, identity and audience

Learn · theory and practice

A digital footprint includes activity traces and content associated with a person. Digital identity is the representation built from that information, including what others publish. An image can reveal a uniform, location or routine without a written name. Combined details allow more inference than each isolated value. Before sharing, ask about purpose, recipients and necessary detail. Not everything we can show is relevant to a task. In class we investigate fictional profiles without requiring anyone to expose their life.

Privacy and security relate but answer different questions. Privacy includes what data we share, why and with whom. Security includes protecting access and information from unwanted use or loss. A well-protected account may reveal excessive details, while a minimal-data post still needs appropriate access. Restricting audience reduces initial visibility, but an authorized person could copy it. Combine content selection, settings and respect for others’ privacy. Demonstrate the setting change on a practice profile and explain its limits without promising complete control over future copies.

  1. Content and context
  2. Inferable data
  3. Purpose
  4. Chosen audience
  5. Remaining exposure
Original diagram · Sintaxis Divergente

A worked example

A fictional profile posts a model photograph with a location and timetable sign behind it. Removing the name from the caption does not remove those image details. The pair reviews what the audience needs to understand the project and adjusts content and audience separately. It can justify reduced exposure without claiming that settings prevent every later copy.

Tu identidad digital depende de ti – IS4K

Published by: Internet Segura for Kids · Open on YouTube

Watch in short sections. Connect one explanation with the diagram and try the example in this section. The written theory lets you complete the activity without playing the video.

The video keeps its original spoken language. Use the captions available in the player if they help.

Your turn

  1. In Google Docs analyze a prepared fictional profile: visible data, inferences, purpose and necessary audience.
  2. Apply a privacy setting in the classroom practice profile and retain before/after evidence without real data; identify any simulation.
  3. In diagrams.net draw post, audience and possible copy; justify reducing data separately from changing access.
Pause and check

Why are removing a location and limiting recipients different decisions, even with a secure password?

↑ Back to the index

6.2. Protect access and recover files

Learn · theory and practice

A password protects access and should be long, unique and hard to guess. Reuse lets one service’s breach affect others. An approved manager can help keep distinct passwords, and another verification factor adds protection, though codes must remain private too. Updates fix known software problems. These measures reduce access risks but do not automatically recover a deleted document. Trials use fictional cards and values; we neither write real passwords nor ask for anyone else’s.

A backup preserves information for recovery. Store it in an authorized destination that the same incident will not destroy. A copy inside a folder does not protect against deleting the whole folder; synchronization alone does not guarantee an earlier version. Restoration means recovering and checking usable content, not merely seeing the same filename. Incident prevention and recovery complement each other. Practice with an identified trial file, preserve an original and recover a disposable working copy. Never use loss of personal files as a test.

  1. Practice file
  2. Authorized backup
  3. Recovery
  4. Opening
  5. Verified content
Original diagram · Sintaxis Divergente

A worked example

A practice copy contains a recognizable sentence. The team retains the original in the prepared destination and restores a working version. It checks the sentence and opens the file. This demonstrates recovery of that content, not protection of every account. A separate permission review investigates who can view or edit it without confusing the measures.

Your turn

  1. In Google Docs connect unique password, another factor, update and backup with the problem each addresses, using fictional cases.
  2. Follow the classroom procedure to copy a practice file, preserve the original and restore the disposable working version from the authorized destination.
  3. Check opening and identifying sentence, record steps and outcome and explain an incident that could affect copy and original together.
Pause and check

What does a verified restoration demonstrate, and what separate protection controls who enters or edits?

↑ Back to the index

6.3. Urgent messages and independent verification

Learn · theory and practice

Phishing uses an apparently trusted identity to obtain information or trigger an action. Fear, urgency or a prize can reduce reflection time. Sender display names and logos are easy to imitate and do not establish identity. An encrypted connection does not prove a site honest either: it protects communication with that site, which could be fraudulent. A request for passwords or codes requires stopping and checking independently, not trying the link to see what happens.

An independent channel means using a known address or seeking a trusted adult without relying on contact details in the suspicious message. Receiving it differs from already revealing information. In the latter case, seek support and act through official account channels, including changing an exposed password and reviewing recovery and access. Deleting a message or hiding a screenshot does not retract information already received. The guide should help without blame or requests for secrets to ‘check security’. Fictional workshop addresses are not links to visit.

  1. Suspicious request
  2. Pause
  3. Known channel
  4. Checked situation
  5. Supported response
Original diagram · Sintaxis Divergente

A worked example

A fictional notice promises game access in exchange for a received code. The team identifies a secret request and seeks a known service channel. It need not open the link to reason about it. If someone already supplied the code, the response includes support and access review; deleting the notice does not address that different situation.

¿Qué es el phishing? | #AprendeCiberseguridad con INCIBE

Published by: INCIBE · Open on YouTube

Watch in short sections. Connect one explanation with the diagram and try the example in this section. The written theory lets you complete the activity without playing the video.

The video keeps its original spoken language. Use the captions available in the player if they help.

Your turn

  1. In Google Docs analyze two fictional messages: request, pressure tactic and missing identity evidence, without opening links.
  2. In diagrams.net draw two routes: received only and data already sent; connect each to independent verification and appropriate support.
  3. Write web guidance explaining encryption and exposed-password response without asking the reader for real data.
Pause and check

Why is the number supplied in the message insufficient as independent verification, and what changes if a password was already sent?

↑ Back to the index

6.4. Respect, support and wellbeing

Learn · theory and practice

Impersonation occurs when someone presents themselves as another person and may be used to deceive or harm. Cyberbullying among minors involves intentional, repeated harm through digital media, rather than an isolated disagreement. Still, nobody needs to wait for a situation to fit a label before seeking help. Affected people are not to blame for others’ harmful actions. Bystanders can offer support, avoid forwarding and approach a school or family adult. Sharing content to discuss it can increase exposure.

Preserve only necessary evidence with adult help and use blocking or reporting where appropriate, without investigating or confronting the perpetrator alone. Those tools do not replace support. Wellbeing also involves attention, rest and relationships: continual alerts can interrupt a task. Useful guidance specifies action and timing, such as silencing alerts during agreed work and checking afterward. This is no universal prescription and requires no logging of classmates’ personal screen time. The guide offers realistic, respectful habits and distinguishes notification settings from responses to interpersonal harm.

  1. Concerning situation
  2. Avoid amplification
  3. Necessary evidence
  4. Adult support
  5. Supported action
Original diagram · Sintaxis Divergente

A worked example

A bystander wants to forward an offensive screenshot for opinions. That can amplify harm despite good intentions. Seeking support with necessary information avoids creating a larger audience. In another case, alerts interrupt a task. Silencing them during an agreed period addresses attention but does not replace the support required for bullying.

Relaciones saludables, también en Internet – IS4K

Published by: Internet Segura for Kids · Open on YouTube

Watch in short sections. Connect one explanation with the diagram and try the example in this section. The written theory lets you complete the activity without playing the video.

The video keeps its original spoken language. Use the captions available in the player if they help.

Your turn

  1. In Google Docs distinguish impersonation, repeated harm and isolated conflict in fictional cases; state a support route without requiring personal experiences.
  2. In diagrams.net draw a bystander’s response avoiding dissemination and connecting necessary evidence, support and blocking or reporting.
  3. Write a wellbeing guideline with action and timing and a respect guideline; explain why they address different problems.
Pause and check

How can a bystander help without spreading harm, and why does blocking not replace seeking support?

↑ Back to the index

6.5. HTML and links between local files

Learn · theory and practice

HTML is a language that describes content structure through elements and attributes. A browser interprets the document to display the page; a search engine, by contrast, locates resources. Within the file, head contains information such as title, while body contains the page content. Language and encoding help interpret text and characters. Elements give the writing a role: h1 identifies the main heading, h2 organizes sections, p contains a paragraph and a creates a link.

A link connects what someone reads with a destination. Its visible text communicates where they can go, while the href attribute gives the address the browser will use. Changing the text does not automatically change that destination. In our folder, index.html, privacidad.html and ayuda.html link through relative paths: ayuda.html is located from the position of the file containing the link. Names, case and folders must therefore match. A difference between the written destination and the actual file can break the route even when the text looks correct.

This relationship between files explains why we test saved pages in a browser and also test the transferred folder. A personal path may work only on its author’s computer; an omitted image may be missing from the received package. Keeping the complete set and its paths allows actual navigation to be checked. Creating HTML files neither publishes a site nor configures permissions. The project is shared in full, including necessary images, within the school’s restricted environment.

  1. HTML file
  2. a element and href
  3. Relative path
  4. Target file
  5. Browser
Original diagram · Sintaxis Divergente

A worked example

A link says ‘View resources’ and targets recursos.html. Changing its text to ‘How to review data’ leaves the destination unchanged. Renaming the file without updating href then breaks it. Comparing name, location and attribute investigates the cause. Repeat testing from the transferred folder to avoid dependence on files existing only on the author’s computer.

Your turn

  1. In VS Code for the Web or the classroom HTML editor create a folder with index.html, privacidad.html and ayuda.html; use the prepared structure and adapt title, language and content.
  2. Add headings, paragraphs and links to the other two pages from each one; save and open in a browser, distinguishing text from href.
  3. In a copy rename a target, reproduce and fix the issue; document cause and retest in Google Docs and check the transferred folder.
Pause and check

What must you inspect when link text is correct but the file is not found, and why is creating HTML different from publishing?

↑ Back to the index

6.6. Accessible images and permitted use

Learn · theory and practice

Including an image in the guide requires knowing which uses are permitted. Finding it online does not authorize every reproduction: we need our own creation, a compatible license or suitable permission. Attribution acknowledges origin, but does not replace authorization. Creative Commons conditions define possibilities: BY requires credit; SA adds sharing adaptations under the same license; NC limits use to noncommercial purposes and ND does not allow sharing adaptations. Knowing the particular license helps determine whether the resource suits our use.

Credit records that origin through creator, title or description, original link, license or permission and changes made. A text alternative addresses another need: communicating an image’s contribution when it cannot be seen. In HTML, src identifies the img file and alt supplies the alternative. An informative image needs its information expressed; a complex diagram may also require a nearby explanation. If an image only decorates and communicates no information, it can use empty alt. Credit and alternative text serve different functions and cannot replace each other.

These decisions contribute to understanding the whole guide. Ordered headings make sections recognizable; readable text and contrast make them easier to read, and link names should anticipate their destinations. Navigating the guide by keyboard and checking understanding without seeing images reveals difficulties a quick visual review can miss. We thus connect permitted resources with information accessible to readers. These checks are useful for improving the guide, without amounting to full accessibility certification.

  1. Resource and purpose
  2. Compatible permission
  3. Credit
  4. Function-based alternative
  5. Checked understanding
Original diagram · Sintaxis Divergente

A worked example

A decorative arrow separates sections while a diagram explains how to seek support. Calling both ‘image’ misses their functions. The diagram needs an informative alternative and nearby explanation if extensive; the arrow may use empty alt. Check credits separately: a useful description does not establish permission to reuse the resource.

Video tutorial 1: Las licencias Creative Commons – parte 1 – Facultad de Humanidades, USAC

Published by: Departamento de Educación Virtual FAHUSAC · Open on YouTube

Watch in short sections. Connect one explanation with the diagram and try the example in this section. The written theory lets you complete the activity without playing the video.

The video keeps its original spoken language. Use the captions available in the player if they help.

Your turn

  1. In Google Docs prepare records for one own image and one compatible external resource with creator, origin, license or permission, use and changes; replace incompatible resources.
  2. In the HTML editor add src and alt according to function; explain complex diagrams in text and separate credit from alternative.
  3. Open the guide in a browser, navigate by keyboard and check headings, contrast and descriptive links; verify understanding without seeing images.
Pause and check

Which different questions do permission, credit and an image’s alternative text answer?

↑ Back to the index

6.7. Ron’s Gone Wrong: from story to guidance

Learn · theory and practice

A story about devices and friendships raises questions about collected data, recommendations and public exposure. Ron’s Gone Wrong is fiction and does not establish how every platform operates. Separate scene description, interpretation and real-world claims needing verification. A friendship recommendation in the story may start a data question, but the guide’s response relies on educational sources. There is no need to copy dialogue or turn the site into a plot summary.

The integrated block retains 0.25 sessions for preparation, 2.25 for authorized viewing or a coherent selection and one for checking, discussion and transfer. The written or described alternative addresses the same problem without out-of-class viewing. Record an ability and question beforehand and three observations during the activity. Then check a claim and turn three situations into guidance on data, relationships or exposure. Each guideline needs a fictional example, action and check. Include conclusions in A01 and implementation in A02. The story activity creates no additional graded submission.

  1. Scene or description
  2. Question
  3. Educational verification
  4. Specific guidance
  5. Guide test
Original diagram · Sintaxis Divergente

A worked example

A story shows a recommendation exposing a character’s information. The pair separates the narrated event from interpretation and asks which data a real task needs. It checks an educational source and writes minimization guidance using a fictional example. Testing asks whether the guide supports that decision, not whether the film describes every social network.

Your turn

  1. In Google Docs record Ron’s Gone Wrong or the alternative: ability, question and three observations about data, recommendations or exposure, without copying dialogue.
  2. Separate observation, interpretation and a checkable claim; verify one using unit sources and identify unresolved questions.
  3. Turn three situations into guidance with fictional example, action and test; include these in A01 design and A02 implementation with equal requirements for the written alternative.
Pause and check

How would you turn an interesting scene into testable guidance without presenting fiction as evidence about a real platform?

↑ Back to the index

6.8. Test the guide and share with permissions

Learn · theory and practice

A useful guide combines content, navigation and protection. Its three pages make privacy, response, wellbeing and credits findable: index can introduce the guide and wellbeing; privacidad develops data and audience; ayuda brings together protection and support. Links connect these parts. Testing them from each page in the final folder checks whether the route works with the files another person will receive. A personal path or missing image can explain why something works on the author’s computer and fails after transfer.

Access answers another question: who can consult or modify that set. In the authorized school service, reader allows consultation and editor allows changes. Restricted access defines the audience, but we need to check the intended role using the prepared trial account, without exchanging passwords. Opening from the author’s session does not demonstrate the reader’s capabilities. The test checks consultation without editing; also reviewing for secrets and unnecessary data connects permissions and content with the intended protection.

Each piece of evidence supports a different conclusion. The protected fictional profile, restoration and fraud and bullying cases show decisions that opening pages alone cannot demonstrate. Asking another pair to find guidance without oral directions lets us observe understanding. A reproducible fault record connects symptom, cause, correction and retesting; an improvement is checked after implementation. Including this evidence and individual explanation in A02 shows what works, what was corrected and why the guide helps its audience.

  1. Checked folder
  2. Restricted audience
  3. Reader test
  4. Unguided use
  5. Verified improvement
Original diagram · Sintaxis Divergente

A worked example

A folder is intended for reading, but a test shows the recipient can change files. The team revises permission and rechecks that role. It then opens pages from the received package. These are different tests: one checks access, the other functionality. Fixing a link does not reduce excessive permission, and restricting access does not repair a path.

Your turn

  1. In a browser follow all three pages, links and images from the final folder; record and fix a fault with retesting in Google Docs.
  2. In the authorized school practice space apply restricted audience and check reader versus editor through the teacher’s procedure; record without account data.
  3. Ask another pair to locate fraud, bullying and wellbeing guidance; improve a difficulty and recheck navigation, fictional profile and documented restoration.
Pause and check

Why does an author test not establish reader permissions, and which two checks separate access from local functionality?

↑ Back to the index

Your project and submissions

A01 · Design the solution

  1. Create CR1-S06_A01_Apellidos in Google Docs with audience, purpose and a diagrams.net three-page map.
  2. Write justified guidance for a located photo, reused password, urgent link, impersonation, bullying and study notifications; integrate Ron’s Gone Wrong or written-alternative conclusions.
  3. Build a first HTML page with checked heading, paragraph and link. In a copy reproduce a broken link, explain its cause, correct and retest.
  4. Adjust the prepared fictional profile and record before, after, audience and limit. Share the draft only in the school space and demonstrate the intended reader role.
  5. Recover and verify a fictional file while preserving the original; explain access versus recovery.
  6. Include a permitted-resource record, sketch, executed microtests, protection and acceptance plan, sources and individual contribution; do not replace completed tests with promises.

What to submit

  • Dossier, map and first editable page; correct link and corrected fault with cause and retest.
  • Six justified guidelines and integrated story or written-alternative transfer.
  • Fictional profile before/after and restricted reader-access check.
  • Recovered practice file with verified content, creator/permission record, plan and individual explanation.

A02 · Web guide to a safe digital life

  1. Complete CR1-S06_guia-web_Apellidos with index.html, privacidad.html, ayuda.html and necessary images; organize privacy, protection and response, wellbeing and credits.
  2. Review the six cases, address an impersonation case and a bullying case and demonstrate the protected fictional profile; include three Ron or alternative transfer guidelines.
  3. Check every link from the submitted folder, keyboard use, headings, image alternatives and compatible credits. Record fault, cause, repair and retest.
  4. Use restricted permissions in the school environment and test reading versus editing from the intended role without exposing account data.
  5. Demonstrate backup and recovery of the practice file with verified content; explain a fictional exposed-password response without treating image concealment as a password change.
  6. In CR1-S06_A02_Apellidos combine expectation, observation and conclusion for navigation, privacy, recovery and help; verify an improvement with another pair.
  7. Submit editable folder, instructions, record and sources. Each partner explains a decision, predicts a result and performs or describes a modification.

What to submit

  • Editable three-page local folder opening with images and checked relative links.
  • Guide with six cases, wellbeing, response and support, three transferred guidelines and permitted resources with alternatives.
  • Navigation, privacy, recovery and help table with corrected fault and verified improvement.
  • Protected fictional profile, reviewed reader permissions, restored file and individual explanation; assessment refers to published rubrics.

Before you submit

  • I explain what a post reveals and distinguish privacy, security and audience limits.
  • I relate protections to access or recovery and verify restored content.
  • I verify messages through another channel and support people without spreading harm or blame.
  • I explain HTML structure, href, paths and link repair after folder transfer.
  • I distinguish permission, credit and alternatives and test reading versus editing.
  • Another pair can find guidance and I justify an evidence-based improvement. These are self-assessment descriptors, not new official criteria or accessibility certification.

Templates and files

Open the blank A01 or A02 template and make your own copy in Google Docs. Keep the editable file from your project platform as well.

These reusable templates help you organise your work. Follow the specific instructions and evidence list for this unit; remove fields that do not apply. The blank master is read-only. Keep your answers private and share them only as your teacher instructs.

A01 · Design the solution

  • Dossier, map and first editable page; correct link and corrected fault with cause and retest.
  • Six justified guidelines and integrated story or written-alternative transfer.
  • Fictional profile before/after and restricted reader-access check.
  • Recovered practice file with verified content, creator/permission record, plan and individual explanation.

A02 · Web guide to a safe digital life

  • Editable three-page local folder opening with images and checked relative links.
  • Guide with six cases, wellbeing, response and support, three transferred guidelines and permitted resources with alternatives.
  • Navigation, privacy, recovery and help table with corrected fault and verified improvement.
  • Protected fictional profile, reviewed reader permissions, restored file and individual explanation; assessment refers to published rubrics.

Classroom rubrics

The classroom assessment reference is preserved below in its original Spanish. Use the checklist above to prepare your work and ask your teacher about any descriptor you need to clarify.

Consultar la rúbrica de A01

Diseño y microprueba

CYR.1.5.1 Estructura y funcionamiento de la guía web

Conocer la construcción de aplicaciones informáticas y web, entendiendo su funcionamiento interno, de forma segura, responsable y respetuosa.

Evidencia. Mapa de tres páginas y primera página HTML con título párrafo y enlace comprobados.

BandaDesempeño observable
1–2,9No identifica qué archivo muestra el navegador ni cómo llega un enlace a su destino.
3–4,9Hay borrador, pero falta una estructura interpretable o la explicación confunde HTML y navegador.
5–6,9Construye una página inicial y explica título, texto y enlace dentro del mapa, usando datos ficticios y recursos permitidos.
7–8,9Comprueba el destino desde otra página y revisa una decisión de estructura que dificulta encontrar información.
9–10,0Justifica una organización alternativa para la audiencia y anticipa cómo conservaría navegación y privacidad.

CYR.1.5.2 Depurar enlaces y rutas

Conocer y resolver la variedad de problemas potencialmente presentes en el desarrollo de una aplicación web, tratando de generalizar posibles soluciones.

Evidencia. Microprueba de enlace correcto y enlace roto con causa y corrección registradas.

BandaDesempeño observable
1–2,9No distingue enlace y destino y no puede reproducir el fallo observado.
3–4,9Identifica un enlace roto, pero cambia elementos sin comprobar la causa ni repetir el recorrido.
5–6,9Reproduce un fallo de ruta o identificador, lo corrige y comprueba el destino en el microprototipo.
7–8,9Explica la regla usada y la aplica a otro enlace de la guía.
9–10,0Diseña una prueba de carpeta trasladada que detecte rutas dependientes de su equipo.

CYR.1.6.1 Autoprotección y respuesta ante riesgos

Adoptar conductas y hábitos que permitan la protección del individuo en su interacción en la red.

Evidencia. Casos ficticios de suplantación y acoso más ajuste de privacidad en perfil de ensayo.

BandaDesempeño observable
1–2,9Recomienda responder con datos o culpabiliza a la persona afectada y no distingue vías de ayuda.
3–4,9Reconoce un riesgo, pero la pauta no permite verificar el mensaje o pedir apoyo.
5–6,9Distingue suplantación y acoso, propone no difundir ni entregar datos y demuestra un ajuste de privacidad en un perfil ficticio.
7–8,9Justifica la comprobación por otro canal y explica cómo conservar solo la información necesaria para pedir ayuda.
9–10,0Aplica la pauta a un caso nuevo y explica por qué recibir un mensaje y revelar una clave requieren respuestas distintas.

CYR.1.6.2 Acceso y publicación con audiencia limitada

Acceder a servicios de intercambio y publicación de información digital aplicando criterios básicos de seguridad y uso responsable.

Evidencia. Carpeta de ensayo compartida con el docente o grupo autorizado y prueba de rol lector.

BandaDesempeño observable
1–2,9Comparte un enlace abierto sin comprobar audiencia o incluye datos que la guía no necesita.
3–4,9Selecciona destinatario, pero no verifica que el permiso corresponda al acceso previsto.
5–6,9Comparte la primera versión en el espacio del centro con audiencia limitada y comprueba qué puede hacer el lector.
7–8,9Corrige un permiso o contenido innecesario tras la prueba desde el rol previsto.
9–10,0Explica qué cambiaría para otra audiencia y prueba el nuevo permiso sin exponer datos personales.

CYR.1.6.3 Autoría y derechos de los recursos

Reconocer y comprender los derechos de los materiales alojados en la web.

Evidencia. Ficha de imagen o recurso con autor origen permiso y uso previsto.

BandaDesempeño observable
1–2,9Considera libre cualquier imagen encontrada y no puede identificar su origen.
3–4,9Cita una web, pero no identifica autor o permiso para el uso previsto.
5–6,9Identifica autoría, origen y permiso de cada recurso inicial o declara creación propia y explica su uso permitido.
7–8,9Distingue citar de tener permiso y sustituye un recurso incompatible.
9–10,0Justifica una alternativa de recurso que permite el uso previsto y conserva una atribución comprensible.

CYR.1.6.4 Protección de archivos y datos compartidos

Adoptar conductas de seguridad activa y pasiva en la protección de datos y en el intercambio de información.

Evidencia. Copia de ensayo recuperada y revisión de datos ficticios y acceso del borrador.

BandaDesempeño observable
1–2,9Confunde tener copia con impedir accesos y no puede recuperar el archivo de ensayo.
3–4,9Copia un archivo, pero no verifica su contenido o no revisa qué datos comparte.
5–6,9Demuestra copia y recuperación de un archivo ficticio y distingue protección de acceso y recuperación de información.
7–8,9Explica una limitación de la copia en el mismo dispositivo y revisa permisos o datos del borrador.
9–10,0Compara un error de edición con pérdida de soporte y decide qué protección necesitaría cada caso.
Consultar la rúbrica de A02

Producto pruebas y mejora

CYR.1.5.1 Estructura y funcionamiento de la guía web

Conocer la construcción de aplicaciones informáticas y web, entendiendo su funcionamiento interno, de forma segura, responsable y respetuosa.

Evidencia. Carpeta web editable, tres páginas conectadas y explicación de HTML y navegador.

BandaDesempeño observable
1–2,9La guía no se puede recorrer y no explica la relación entre archivos y enlaces.
3–4,9Abre alguna página, pero faltan destinos o usa datos o recursos sin revisar.
5–6,9Construye las tres páginas, explica su funcionamiento y permite localizar las pautas con textos claros y recursos autorizados.
7–8,9Revisa un recorrido completo con otra pareja y corrige una barrera de estructura o comprensión.
9–10,0Adapta una sección a otra audiencia y demuestra que mantiene funcionamiento, fuentes y protección de datos.

CYR.1.5.2 Depurar enlaces y rutas

Conocer y resolver la variedad de problemas potencialmente presentes en el desarrollo de una aplicación web, tratando de generalizar posibles soluciones.

Evidencia. Registro de fallo corrección y nueva prueba de enlaces en la carpeta de entrega.

BandaDesempeño observable
1–2,9Mantiene rutas que impiden la consulta y no puede explicar su origen.
3–4,9Repara un enlace por ensayo, pero no verifica los restantes ni el archivo exportado.
5–6,9Localiza y corrige un problema de ruta y repite la prueba desde la carpeta entregada, explicando la solución.
7–8,9Usa la misma regla para revisar todos los destinos afectados y comprueba otro recorrido.
9–10,0Detecta un fallo nuevo al trasladar la carpeta y generaliza una pauta de rutas relativas que evita repetirlo.

CYR.1.6.1 Autoprotección y respuesta ante riesgos

Adoptar conductas y hábitos que permitan la protección del individuo en su interacción en la red.

Evidencia. Pautas web justificadas, resolución de dos casos y demostración de perfil protegido.

BandaDesempeño observable
1–2,9Las pautas exponen a la persona o no ofrece una respuesta adecuada a los casos trabajados.
3–4,9Nombra consejos, pero no los aplica al caso o no sabe mostrar el ajuste de privacidad.
5–6,9Aplica una pauta de verificación y ayuda a los dos casos y demuestra privacidad en el entorno ficticio.
7–8,9Compara alternativas y justifica una respuesta que reduce exposición y facilita apoyo.
9–10,0Resuelve un caso nuevo sin difundir datos y explica qué debe consultar al adulto o responsable del centro.

CYR.1.6.2 Acceso y publicación con audiencia limitada

Acceder a servicios de intercambio y publicación de información digital aplicando criterios básicos de seguridad y uso responsable.

Evidencia. Entrega o publicación interna y registro de permisos y acceso de lector.

BandaDesempeño observable
1–2,9La entrega expone información innecesaria o no permite controlar quién accede.
3–4,9Usa el espacio previsto, pero conserva permisos excesivos o no distingue ver de editar.
5–6,9Accede y entrega por el servicio del centro, limita audiencia y verifica lectura frente a edición y ausencia de datos innecesarios.
7–8,9Corrige una incidencia de acceso y contrasta que el destinatario previsto puede consultar sin privilegios añadidos.
9–10,0Justifica la adaptación a otra audiencia y explica por qué retirar un enlace no elimina todas las copias ya difundidas.

CYR.1.6.3 Autoría y derechos de los recursos

Reconocer y comprender los derechos de los materiales alojados en la web.

Evidencia. Créditos de textos imágenes y otros recursos realmente usados en la guía.

BandaDesempeño observable
1–2,9Usa recursos ajenos como propios o no reconoce que su reutilización tiene condiciones.
3–4,9Hay créditos parciales, pero algún recurso no tiene origen o permiso comprobable.
5–6,9Cita autoría y procedencia de los recursos y aplica sus condiciones de uso y modificación.
7–8,9Revisa un recurso reutilizado o modificado y corrige una atribución o condición que faltaba.
9–10,0Compara opciones de licencia para un recurso y justifica una selección coherente con el modo de compartir la guía.

CYR.1.6.4 Protección de archivos y datos compartidos

Adoptar conductas de seguridad activa y pasiva en la protección de datos y en el intercambio de información.

Evidencia. Recuperación demostrada, carpeta revisada y respuesta a exposición de una clave ficticia.

BandaDesempeño observable
1–2,9No recupera información ni distingue publicar un secreto de eliminarlo de una captura.
3–4,9Mantiene copia, pero no prueba apertura o propone solo borrar la imagen tras exponer una clave.
5–6,9Recupera un archivo y comprueba contenido, limita datos y explica cómo pedir ayuda y cambiar una clave ficticiamente expuesta.
7–8,9Verifica versión recuperada y justifica qué riesgo sigue pendiente con la copia y los accesos usados.
9–10,0Resuelve un caso nuevo de pérdida o exposición y selecciona medidas activas y pasivas explicando sus límites.

Videos, resources and sources

Cibertips Para, Piensa, Conéctate: 5 Consejos para una vida digital sana

Published by: Fundación Cibervoluntarios · Open on YouTube

Watch in short sections. Connect one explanation with the diagram and try the example in this section. The written theory lets you complete the activity without playing the video.

The video keeps its original spoken language. Use the captions available in the player if they help.

Keep learning

Editorial revision: October 2026.